Additional Where Clause issue
Posted: December 30th, 2022, 12:20 pm
Additional Where Clause issue(MVC):
I have found a few Inquire services that have issues with the where clause.
When run, the query will duplicate the where clause piece that was the old Additional Where Clause. Except that the xslt doesn't work on the duplicate. So the example is for-each on some item data. The result is something like this:
ItemNumber = '1001' or ItemNumber = '1002' or ItemNumber = '1003'
and
ItemNumber = '' or ItemNumber = '' or ItemNumber = ''
The only way fix this is to recreate the inquire service.
You can recognize these only by
1. Noticing that your query has a strange duplicate section of where clause.
or
2. Opening the service, clicking the top part of the inquire, and seeing the Additional Where Clause in the build data.
From this viewing of the service, you can see the Additional Where Clause as well as the same thing converted into an actual where clause block.
Help for a fix needed:
1. I am unsure what caused this. Base MVC EASYCommerce just switched xml processing modes from legacy to current. Maybe that?
2. Is there a way to affect all of these services so that this is fixed without having to manually change all Inquire services this way?
3. At the very least, is there a way to identify each affected query so a manual change can be made?
I have found a few Inquire services that have issues with the where clause.
When run, the query will duplicate the where clause piece that was the old Additional Where Clause. Except that the xslt doesn't work on the duplicate. So the example is for-each on some item data. The result is something like this:
ItemNumber = '1001' or ItemNumber = '1002' or ItemNumber = '1003'
and
ItemNumber = '' or ItemNumber = '' or ItemNumber = ''
The only way fix this is to recreate the inquire service.
You can recognize these only by
1. Noticing that your query has a strange duplicate section of where clause.
or
2. Opening the service, clicking the top part of the inquire, and seeing the Additional Where Clause in the build data.
From this viewing of the service, you can see the Additional Where Clause as well as the same thing converted into an actual where clause block.
Help for a fix needed:
1. I am unsure what caused this. Base MVC EASYCommerce just switched xml processing modes from legacy to current. Maybe that?
2. Is there a way to affect all of these services so that this is fixed without having to manually change all Inquire services this way?
3. At the very least, is there a way to identify each affected query so a manual change can be made?