switchtolayertheme multiple times in a workflow generate alert
Hi,
I have this workflow which allows user to pick a layer theme, which was passed to the external command: switchtolayertheme. In the end of the workflow, I want to run the swtichtolayertheme again if the user has set the theme to a non-default layer theme.
Whenever this happened, there is an Alert saying "There was a workflow error running activity: Unable to get property 'gcxLayer' of undefined or null reference". The layer theme is switched back, but how can I get rid of the alert?
It seems like this message will show up whenever switchtolayertheme command is run too many times in the workflow. But in my workflow, it is a requirement. Whats a work around? Thanks a lot in advance
0
-
Correction: The workflow is actually disabled totally after seeing this message. rerun the workflow will throw the same error. The only way to stop it is to refresh the map service. 0 -
Can you post your workflow so we can take a look at it? 0 -
Of course John.
There is a maximum character for respnoses, I cant copy and paste my workflow here without cutting it up. I have uploaded it thorugh dropbox. Let me know if you can access the file below. If not, could you give me your email. I can share the workflow to you via email. Thanks a lot.
https://www.dropbox.com/event_details/630540596/1372656977/598898941/00 -
It looks like I don't have access to the link.
john.nerge@brooklynpark.org0 -
Update for anyone reading this post: we didn't find a solution, and it seems more like a glitch than a workflow issue. 0 -
I am having the same issue with a workflow. I can use the "SwitchToLayerTheme" one time, but run it again (same exact command) and I get an error. Was the glitch in the workflow or the activity? 0 -
Technically I think it was the specific activity, i.e., you could remove it and rerun the workflow without errors, but without the activity the workflow is pointless since it won't switch the layer theme. It's a good ol' Catch 22. 0 -
Tech support helped me resolve my issue, but it did take a while to nail down. The issue was that there was too much back and forth between the client and server. Once we moved the task to reduce that traffic back and forth, it worked. So, we did not make any change to any of the activities, we just moved the SwithtoLayerTheme to a different place in the workflow. You may want to give that a try. 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
8 Kommentare