Hi,
AX Version: 2009
Application version: Release, fresh VM installed and downloaded demo data from Partnersource
We are facing an issue where in we cannot use asterisk (*) after a string to indicate a wildcard for workflow conditions. Say we are looking for items that DOES NOT start with 11 then we would use IS NOT value 11* for workflow conditions.
The problem is workflow is treating the string as a whole (like 11* not 11 then leading characters) which is still an assumption based on testing (i hard coded the item number and it did meet the criteria) so please correct me here if mistaken.
Sample data.
I have 3 purchase requisitions
Reqid 10001 with itemid 1102
Reqid 10002 with itemid 9101
Reqid 10003 with itemid 8009
Now i created a standard workflow as shown below
So, when i add a condition (as shown below), where PurchaseLineRequisition.Item Number "IS NOT" value 11*
I was hoping that AX will read it as a condition where ITEMS that DOES NOT (which are Req10002 and Req10003 ) start with 11 will be true and ITEMS that DOES (req10001) start with 11 will be FALSE, instead it returns TRUE to both.
Req10002 and Req10003 TRUE
now REQ10001 where in the ITEM is 1102 should return false because we are expecting that it should NOT meet the workflow condition IS NOT value 11* but instead still returns TRUE because what we think is that it does not recognise the use of ASTERISK as wildcard as part of the search string.
Can anyone confirm if this is a limitation to Dynamics AX 2009 workflow or if there is a step we are doing wrong here? :) Would appreciate the help a lot (and promise to confirm the answer once verified :) )
Many thanks,
Reynaldo
