Skip to main content

Parcel Search workflow, token error, Filter Workflow URI

Justin Kraemer
I have a parcel search workflow operating flawlessly on a secured map service. Frustratingly it no longer does so the moment I set a Filter Workflow URI on the parcel layer it queries. While the Filter Workflow URI correctly manages the map content, the parcel search always fails at the QueryTask, reporting "Invalid Token". What's more, before the search workflow reaches the QueryTask, the autocomplete form fields no longer populate.

 

If I remove the Filter Workflow URI, the workflow functions properly again.

 

I don't understand why the Filter Workflow URI has this effect, but wish to learn how I can enable the search workflow while it is in place. I suspect something about permissions is impacted by Filter Workflow URI, but I can find no documentation explaining this. I need some help, please.

 

Thanks,

 

Justin
0

Comments

4 comments

Date Votes
  • Justin Kraemer
    Further to my Nov 26 post, I today tried simplfying the workflow to run just the address search, and it behaved the same way (no autocomplete and an invalid token error. Why do tokens fail when there is a filter workflow URI in place? Would it help if I post the xaml content here?
    0
  • Permanently deleted user
    I'll take a look at it if you want to post it
    0
  • Permanently deleted user
    So is you ask address form working but your query task isn't?  I guess I'm a little unclear on where it is failing and I'm unable to test it without credentials.  Would you be willing to set up a temporary login/password or create a token for me to try?  If you'd like, you could send them to my email so it won't be posted here: mboyd@miottawa.org
    0
  • Justin Kraemer

     

    With Marshall's help I was able to get the workflow working. The trick was to use GenerateToken using ArcGIS Server credentials that allow access to the secure services on the rest endpoint. In what I posted above, I was using GetMapServiceInfo, which creates a token using the credentials of whatever user is runing the workflow, hence the invalid tokens.

     

    My data link problems were due to the fact the site I was working on was made by reference to another one. This meant the each data link name is prefaced by the name of the site being referenced, plus a "-". By updating the data link names in the feature descriptions, the values displayed properly. It's too bad these don't autoupdate when a site is created by reference.

     

    Great thanks to Marshall Boyd for his superb help in solving my problems!
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post