I have a ModelBuilder process which carries out the following (diagram attached):
When run 'in person' in ArcGIS Pro, the model runs without issue. However, it fails when run as a Scheduled Task, giving the following error:
ERROR 000358: Invalid expression
Failed to execute (Select Layer By Attribute).
The error help page is not particularly useful in this instance. Any ideas?
Glad you got it working. My field is not numerical but it still fails unfortunately.
I see, might be a separate issue then for hosted layers (I was working on local file geodatabase/SDE).
I did check though and I have a scheduled model tool (ArcGIS Pro 2.9.2) that has a bunch of "Select Layer by Attribute" (non-numeric field) and its been working, the thing though is I am working on a file geodatabase then overwriting my feature layer after am done with my geoprocessing.
You might want to try creating a local copy of your "feature layer" and use that as input for your model after you are done you can overwrite your feature layer or do a delete rows/append to just insert the records that have changes.
Thank God I found this thread.
I also have been going crazy with this. Modified my model, my script, nothing worked when scheduling this to update a hosted feature layer. Manually it works perfectly.
I am not too frustrated as this has to run monthly, but man it can drive you nuts not knowing that is a bug.
Running on 2.9.3 right now.
I think 3.0 was released today.
I installed 3.0 today and go figure I am still having issues. Now a new error message shows up, have you had a chance to install and try out the scheduler with 3.0?
Hi Michael, not I have not.
I was about to when I asked my GIS IT group if it was OK and they told me not to as it may also have issues. To wait until a further release is available.
Go figure, a release to fix the release that was to fix a previous release.
I will wait to see when I can install it and then let you know.
Sorry to hear you still have issues.
I've carried out some limited testing so far using 3.0 and it seems to have resolved the issue. I will report back if that changes though with further testing.
What's the new error message @Michael_VanHatten ?