Latest Contributions by StefanDieters

We had a very similar problem in directing path logic. I tryed many of the same things as you have, with a similar lack of success.It was a problem with how == >= is interpreted. see rest. This is my answer to a similar problem see: https://community.esri.com/t5/arcgis-workflow-manager-questions/quot-send-web-request-quot-step-error/m-p/1237671#M1757 Here is the explanation from our (esri.australia technical rep Razi Mosadeghi). I have verified that the suggested fixes work Please find below the explanation they have provided on why Boolean(jobExtendedProperty($job, 'switchtable', 'nerrors')== 0) Does not work: It appears == 0 returns the string representation of the value here and not the actual value (an integer). In addition, core Arcade logic is playing a role here as well. In Arcade, the > and < operations will first try to evaluate the result as a string value. If that fails (because you aren't using a string), it will then try to evaluate the result as a integer, which is what we are using here. The == function doesn't have that same logic. It tries to compare a string to a string and then will fail if it can't. So, if you would like to use == 0 logic, we would need to do either one of the following: Use Number(jobExtendedProperty($job, 'tablenew', 'arcade')) == 0 when using an integer value Or, use jobExtendedProperty($job, 'tablenew', 'arcade')) == '0' if you are ok with using a string representation of the value This is my answer to a similar problem ... View more

Can't tell exactly what you want. Maybe use an extended property for your date string and arcade to change the input parameters of the send web request step and then test the output of the web request step to branch your workflow creating a loop and exit in your overall workflow.   ... View more

Last piece of puzzle: Thanks Razi of Australian esri support. It appears == 0 returns the string representation of the value here and not the actual value (an integer). In addition, core Arcade logic is playing a role here as well. In Arcade, the > and < operations will first try to evaluate the result as a string value. If that fails (because you aren't using a string), it will then try to evaluate the result as a integer, which is what we are using here. The == function doesn't have that same logic. It tries to compare a string to a string and then will fail if it can't. So, if you would like to use == 0 logic, we would need to do either one of the following: Use Number(jobExtendedProperty($job, 'tablenew', 'arcade')) == 0 when using an integer value Or, use jobExtendedProperty($job, 'tablenew', 'arcade')) == '0' if you are ok with using a string representation of the value ... View more

Thanks for checking. I later realized that error and updated the expression. Did not work either. ... View more

Instead of using joboutputvalue I put errorsIdentified into extended property table and use jobExtendedProperty($job, '<table_name>', '<field_name>'. With the table visible I am sure of the value going into the branching. I have made some progress.If I use the expression : Boolean(jobExtendedProperty($job, 'switchtable', 'nerrors') > 0) on the path back to the editor, that works. However the path errorsIdentified (nerrors in table switchtable) = 0 is never executed. ... View more

Many replies have suggested switching to python. Python doesn't do every thing VBA scripts could do ... low level arcobject control. You can get that with VB.Net or C#. If you know VBA then going to VB.Net is not such a great leap. My role has been converting our VBA ArcMap customizations to VB.NET. They involve a lot of arcobjects. I started out knowing some VB. I used the venerable book "Getting to Know ArcObjects" to get how arcobjects work. There are many little changes, but these get to be routine. Some relate to changes in VB from VBA to .Net, and some are specific to esri. Converting the use of Variant to  Object can be a pain. However the biggest changes are in Windows forms e.g. how treeviews are traversed has been substantially changed. The other area of knowledge upgrade was getting fully into object orientated programming paradigm which is not really are the core of VBA. This changes the way you program .... ... View more