I need to add a new (outer-joined) data source to a query used by an existing workflow in AX2009. If I just did that, I would get the following error when opening an existing workflow configuration: The value "MyTable" is not found in the map.
The error comes from SysExpression::validateProjection(), which validates whether workflow conditions can still be applied to the query and it doesn't accept additional data sources.
I see several options how to deal with that and none is perfect, so I want to ask whether somebody dealt with the same problem before.
- I could delete the existing configuration and create a new one (as suggested on Technical Support blog). Nevertheless it wouldn't be such simple in real life, because there will be many instances of the workflow still running.
- I could create a new workflow template and a new document returning the modified query. The original workflow wouldn't change at all. That sounds like the safest option, the drawback is that I would end with two templates for the same thing, which would make configuration a little bit harder.
- I could modify expressions saved in ExpressionTable. Because they're saved in XML, it shouldn't be too difficult, but there is a risk of doing something wrong.
- I could change the standard logic to accept such changes in queries. It seems to me that adding an outer-joined data source shouldn't break anything, but who knows, so I'm not too keen to touch it.
- The workflow document could return different queries for different workflows based on the same template, but it sounds like asking for troubles sooner or later.
- I should stop here, I'm getting weirder and weirder ideas. :-)
"1" would be without any work for me, but it would be a problem for users. "2" is what I'm currently intending to use. "3" would be cool but probably not worth doing. "D" and "E" look like something what could easily fail.
Any comments? Did I miss any useful option?