Workflow List Box Doesn't Populate - Bug?
Hi everyone,
I have got two list boxes which populate their fields based off an identical query to an arcgis feature layer endpoint.
The problem I'm experiencing is that the first workflow you activate populates the fields that I would expect it to however the second one will not. If I click on the second one again (once or more times) then it will populate. If I point one at our test server and one at our dev server then they both populate fine. I also tested it with a dropdown box and got the same problem too. (replicated it on multiple sites also)
This looks like a bug to me. What does everyone else think?
-
I've read elsewhere in these forums that there is an arcgis server bug, where the second identical request to an arcgis server endpoint will intermittently fail. That would explain why your boxes populate when pointed at different servers. What about putting a 1=1 wherelcause on one and not the other - not sure if that would constitute a different request but generate the same response.
James
0 -
James, I just tried that now and it didn't fix my problem. It would be nice if it did because it would be a lot less effort.
I found that if it is a table instead of a feature at the REST endpoint then everything works fine. So now it looks like I will have to create a lookup table for every rest endpoint I want to query and make a list box off. It's a bunch of overhead but at least it works :p
Still unsure if it's an Arc error or not though.
0 -
Hi Matt,
Do you get the same behavior when you run your workflow in the simulator?
You may want to build a small test workflow if there are lots of client activities that don't render in the simulator.
If you do see the same behavior, you can run fiddler while running the simulator and watch the requests being sent from the form to the server. That usually helps determine what is happening.
Regards,
-Malcolm
0 -
Hi Matt,
A couple of details can be found on ESRI's website at http://support.esri.com/en/bugs/nimbus/TklNMDg2MzQ5
As far as I'm aware, this issue only affects 10.1 SP1 servers and is resolved in 10.2.
regards,Edmond
0 -
Thanks for the replies guys,
The simulator doesn't suffer from the problem because it only occurs when two workflows with the same query are in the site. After looking at what Edmond has posted I am confident that it won't be fixed until we upgrade to 10.2. That isn't scheduled in for a while so I'll try to remember to come back and update this with what happens.
0
Please sign in to leave a comment.
Comments
5 comments