Modelbuilder If Falue Field Is

SarahHartholt

I'm attempting to use the If Field Value Is logical tool to append an AddressPoint to an ApprovedLicense feature class only if the IssueLicense field is 'yes'. 

My current workflow includes reading in the AddressPoint feature class and iterating over the ID field. I perform some calculations on the feature including populating the IssueLicense with 'yes' if a series of conditions are met. I run my model and stop it after  a few iterations to see if it is performing as expected. The field calculations return correct values but I can see that the first 6 address points are appended to my ApprovedLicense feature class even though only 3 have 'yes' values in the IssueLicense field. Can someone tell me why this is happening?

 

 

 

KimberlyGarbade

I put together this example.  Maybe it will help.  Sorry, this might get long:

Let me say first I'm using test data and couldn't do all the processing that you did, but I think it's a decent representation of the steps I'm thinking about.

I had a small Feature Class containing 5 test points (TestPoints - red dots) and created another feature class of 5 points called CloseTest (Green Dots) tables for both are below (before running the model)

 

You can see they both contain an address field.  I'm going to append the records from "CloseTest" that have a "Criteria" equal to "Yes" and that are farther than 10 feet away from a point in TestPoints back into TestPoints.  In this case I want to add 25 Pebbles Wy and 40 Not Close St (33 Kim Crt meets the distance requirement but its criteria is "n/a", so it fails the criteria test).

note: I just manually set the criteria, but I think this part is working for you so no big deal.

To do this I had to use three models (and just for the record let me say here that model builder is great for small things, but I don't like it when it starts getting complicated like this. It just seemed harder than writing python would have been)

Model 1

Model 1 creates a blank feature class into which I put just the points from CloseTest that meet my criteria test.  I just used Create Feature Class to copy the schema of CloseTest.  I call the empty feature class PotentialAppendRecords.  Model 1 then calls Model2.  This is a submodel containing an iterator that iterates over all of my CloseTest records and appends them into PotentialAppendRecords if they meet my criteria of "Criteria = 'Yes'".

The result of Model 2 is a feature class containing 4 records that meet my criteria, it is set as a parameter in Model 2 so it will be returned in model 1 as the output of Model 2 (I hope that makes sense - it shows up as "PotentialAppendRecord(#)" in model 1).  PotentialAppendRecords then gets passed to a Near tool in Model 1.  This adds attributes to PotentialAppendRecords that indicate how close it is to a feature in TestPoints.  I use 10 feet search radius, so anything outside of that gets a -1 value in NEAR_DIST:

 

We can see that two records in PotentialAppendRecords are farther than 10 feet from a record in TestPoints.  All model 3 does is append those 2 records in TestPoints.

I hope this helps.

Since I've been this long winded I'll say that to me it didn't seem like Model 3 should be needed, but if I didn't include it the iterator in model 2 would run the Near in Model 1 5 times and the append would not work, but when I isolated the append in its own model and passed PotentialAppendRecords to it as a parameter it worked.  I think I know model builder pretty well and it still confuses me sometimes.