I stumbled upon the solution when I decided to just let my model run to see what happened. Apparently, the first iteration used the value '1' and all my selections were empty because of this. After the model finished for the value '1' it started to iterate through the actual values. Worked perfectly!
you can eliminate the initial run by constructing your model such that the iterator is the first process to run, thus it gets initiallized to the value you want.
I was wondering if anyone has figured out a work around for this issue. I am running into the exact same problem.
A simple model - Iterate field value (Name)- use the string output value to run a Make Feature Layer (Name =%Value%)
It will run and immediately stop with the error message Name = 1 does not exist. Examining the model after it ran, it shows that the Value output for Iterate field value now equals 1 even though that value does not exist in the data.
I even tried running the Iterate field value by itself after this happen and it gave me the same result Value = 1.
A this point I closed everything down, opened it back up, ran the same model with no changes and it worked, once, and then went back the Value = 1 issue.
Any help with this would be appreciated.
Thanks
Thanks!
Shitij
Here's an image of the model, table and parameters.
What bothers me is the inconsistency of the model, it will run fine one moment and then switch to the problem I have mentioned above, without me changing anything.
The way I managed to make the model work the last time is to change the Input value from the drop down option (the layer is in my table of contents) to the hard drive location using the browse button.
That fixed the problem without me having to change anything else in the model.
What you are describing is an inconsistent behavior and a bug with reading a layer, unfortunately i am unable to reproduce it with the current version. Which ArcMap version do you have?
I am using ArcGIS 10.5.1