"Send Web Request" step error

sirishb

Hi All,

ArcGIS enterprise version: 10.9.1 & ArcGIS Pro V 3.0

We are using ArcGIS Workflow Manager Server (service-driven).

When we try the following REST Query URL in browser

Input URL-1:
https://sampleserver6.arcgisonline.com/arcgis/rest/services/SampleWorldCities/MapServer/0/query?where=POP+%3D+521934&returnCountOnly=true&f=pjson

Output result:
{
"count": 1
}

We have created simple workflow diagram using "Send Web Request" step and configured the above mentioned Input URL-1, getting the output result ("count": 1) as expected.

---------------------------------------------------------------------------------------------------------------------------------------------------

When we try the following REST Query URL in browser

Input URL-2:
https://sampleserver6.arcgisonline.com/arcgis/rest/services/SampleWorldCities/MapServer/0/query?where=POP+%3D+1&returnCountOnly=true&f=pjson

Output result:
{
"count": 0
}

We have created simple workflow diagram using "Send Web Request" step and configured the above mentioned Input URL-2, getting the following error and unable to proceed with the next steps.

We have chosen "Expressions" under Path Logic options. 

Expected behavior: we should get the output result ("count": 0)

Appreciate any help on this. Thanks.

Regards,

Sirish

StefanDieters

We had a very similar problem in directing path logic. 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:

1. Use Number(jobExtendedProperty($job, 'tablenew', 'arcade')) == 0 when using an integer value
2. Or, use jobExtendedProperty($job, 'tablenew', 'arcade')) == '0' if you are ok with using a string representation of the value