Geodatabase Version Not Honored in VGS Web from Workflow?
I am running the same WF in both WAB on prem and VG Web on prem. The WAB app honors the Geodatabase Version used in the WF's Query Layer activity, while the same exact WF in VG Web does not. WF Version 5.31.0 and VG Web 5.21.0.
When I print the number of records found (via an Alert), the number is correct and reflects what REST end point query gives me in WAB. The number is incorrect and defaults to the sde.DEFAULT Geodatabase Version.. as if there was no value there.
Also seeing some weird things in VG Web where a GP service returns json as a list, which is no prob in WAB, but the WF fails in VG Web... as web traffic says the JSON returned is invalid.
Anyone else seeing either of these issues?
-
Also, the numbers of records returned is correct in the WF > Sandbox UI... I think this is a bug with Web and will open a support case.
1 -
I saw some discussion around this internally, folks are looking into it.
Outside of Workflow; there is a command you can use in Web to specify what gdbversion you want to point to ... that allows the ootb editing tools to be used on a gdbversion other than current if desired.
0 -
Good to hear Cam. The task of the WF at hand is really just to re-draw the features for a particular gdbVersion. I am just passing what is needed into a web tool via GP service and returning the features to the screen that way... for now
0
Please sign in to leave a comment.
Comments
3 comments