Select to view content in your preferred language

Field Value Iterator and Select is Broken..

4062
14
Jump to solution
03-24-2016 09:35 AM
StevenGraf1
Frequent Contributor

I have a model that iterates over unique field values and uses the select tool to output features as shapefiles using the unique value as the naming convention. It works....sort of.  It runs through the entire iteration but only outputs the first 2 results.  The first 2 results are correct but where are the rest of my files going?!  Attached is my toolbox.  You can use any data you want in it.

Using version 10.2.2.

-Steven

0 Kudos
14 Replies
ChrisDonohue__GISP
MVP Alum

An observation:  shouldn't there be a tie from Iterate Field Values back to the Select function?  Like from Value to Select?  Or is that buried in the Select?

Chris Donohue, GISP

0 Kudos
StevenGraf1
Frequent Contributor

I was using the value in the selection expression such as Stream = '%value%'.  Using apostrophes was the only way to get it to work because my values were strings.  I assume it is trying to select where the stream name actual equals %value% instead of the actual field value.  I tried simply assigning the value field back into the expression but it would error out.  I tried building it a couple different ways using make feature layer and select layer by attributes but none of them would output the geometry.

-Steven

0 Kudos
StevenGraf1
Frequent Contributor

So this is definitely an issue with 10.2.2.  I just ran the iterator with select on version 10.4 and it works perfectly.

-Steven

0 Kudos
DanPatterson_Retired
MVP Emeritus

http://downloads.esri.com/support/downloads/other_/104-IssuesAddressedList.pdf

there is a document for 10.3... check to see it was an issue, whether it was reported and/or whether it was solved.

StevenGraf1
Frequent Contributor

Thanks for the link.  I looked at 10.3 and this NIM was addressed.  NIM098729 In ArcGIS for Desktop 10.2.1, when running a model with the Iterate Feature tool, an incorrect number of outputs are generated only when running the model as a tool.

I assume this when it was fixed.  I didn't see it in the 10.4 docs.

Anyways, its fixed in 10.4.

-Steven

0 Kudos