What does "SqlQueryUnsafe activity has not been implemented" mean for my server workflow?
I'm calling a server workflow from a client workflow. I'm getting an error:
[WF: activity not implemented] The gcx:wf:server::SqlQueryUnsafe activity has not been implemented.
What am I missing?
-
This means that your server workflow is being interpreted as a client workflow and the browser is trying to run it rather than asking the server to do it.
The gcx:wf:server::SqlQueryUnsafe activity indeed does not have a client implementation so the error message is spot on, but you'd have to know that the workflow is running in the wrong context for this message to make any sense.
So... why is your workflow not being recognized as a server workflow? I've seen this happen if:
- You have exported the server workflow to JSON and are hosting it in a virtual directory rather than in portal. This pattern is not supported for server workflows. You must use portal items for server workflows.
- You have manually edited/copied the workflow portal item. Server workflow portal items have two properties "isServerWorkflow" and "serverUrl". These are what tell the Run Workflow activity that it is a server workflow. If you do some manual portal item manipulations these could get lost.
--Ryan
0 -
Thanks, Ryan. Somehow my workflow decided it was a client workflow. Even though I created it as a server workflow, used many server workflow activities to build it, it changed its type to client. I haven’t exported or copied it. I just shared it in AGOL. Is there some series of steps I should avoid to keep from changing my workflow type from server to client? Other than manually changing the type, of course . . . 0 -
Hi Sean,
I haven't seen this happen through the normal use of the Designer. If you keep seeing it please let us know.
--Ryan
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare