Different behavior/results from workflow between a base site and a referenced site
We have a functional workflow that queries a table to find street intersection points. The table has STREET1, STREET2, X, Y fields. We use a DisplayForm task to auto-populate, select, & pass the input entry/argument, using " UPPER (QueryField) like UPPER('%{0}%') " in a WHERE clause & queries for matching STREET2 results. We use an input argument to set the appropriate MapServiceID (modified to accurately reference the map service ID of the site config). Layer REST endpoint is hard-coded.
Have had this working in an existing site with multiple viewers. We've built a new site that refers to and uses this preexisting site as a base, with "extra" datalayers on top. The workflow config in the new site is set to reference the exact same workflow/copy of the XAML, and the property set to deal with the system modified MapServiceID.
The workflow's search works properly for the existing site: Invoking the workflow, entering the first name (e.g. 'main') will auto-populate / return matching records (e.g. Germain St & Main St). Selecting an entry will successfully return matching intersecting streets from the second field.
On the referring / failing site, entrering a (partial) term (e.g. 'main') branches to the "No Matches" branch of the workflow. But if the properly syntaxed value (complete/spelling/case; e.g. 'Main St') is entered, the auto-populate doesn't display but the query will work and return the expected intersection results.
Repeating, the same XAML file is invoked. And the fact that you can enter an exact value and the query works indicates the correct map service & data layer is accessible. There just seems to be some issue with the DisplayForm task correctly using the aforementioned "UPPER (QueryField) like UPPER('%{0}%')" definition. I wondered if it was related to scope to the DisplayForm's Output Argument, but switching scope between sequence and flowchart made no difference.
And the workflow executes properly in the simulator as well.
Anyone have insights on this?
Thanks!
Please sign in to leave a comment.
Comments
0 comments