Latest Contributions by KimberlyGarbade

I wrote a constraint rule (first image below).  In the second image below you can see I added an attribute called DomTest to some test data.  I applied a domain call WetDry to that field.  Only a value of "WET" or "DRY" is allowed by the domain.  I then selected one record and used the field calculator to populate it with "KIM" (a clear violation of the domain) and it let me. After I applied the constraint rule I tried to update one record again using the field calculator.  This time using "TIM" and the constraint rule stopped the edit.     ... View more

Odd. But maybe this is a clue: So maybe something like:  concat('XX',valueOf(ObjectID))  or concat('XX',Trim(valueOf(ObjectID))) or 'XX' + valueOf(ObjectID) Even though it says on the same page that "The toString( ) and valueOf( ) functions wrap identical implementations." ... View more

I'm not seeing the attached error.  Would it be possible to repost it please? ... View more

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. ... View more

Would you share the piece of your code that is creating/using the connection and tell us what environment your creating and running the python in... python window, notebook, Spyder...? ... View more

Can you provide a screen shot of the calculation your running? Almost sounds like a TOP keyword is being used somewhere (in SQL Server) or like the system (either on the database end or on the client side) is running out of resources.  I.E. its doing its job in 40 row chunks and it fails after the first one because it runs out of memory or diskspace...  ... View more

I found a discussion on this topic on Stackoverflow, where someone else had the same problem.  I'm posting a link to the python docs thy post references below. I didn't want to paste a link to the post itself (I know people have security concerns) so I'm pasting images below that get to the "good parts" of the post.  The first is a description of the problem, the second the suggested solution: Issue from link: Solution from link: Python docs:  https://docs.python.org/2.7/howto/unicode.html ... View more

Good Morning... If this is what you are referring to I don't think the data has to be coming from a feature service.  The sample data referenced in the article is just a file GDB. https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/advanced-gdb-attribute-rules-editing-external-features-with-attribute-rules/ ... View more

Since you clipped your points with your polygons already you can use a spatial join to merge the attributes of your points with the attributes of your polygons. You can turn fields on and off in your polygon layer's  properties to limit which attributes are merged. https://pro.arcgis.com/en/pro-app/2.8/tool-reference/analysis/spatial-join.htm ... View more

An Esri person would probably know the specifics, but I would imagine its just the way the objects are structures. You need Geometry to get the "shape" of the feature.  This is probably stored in a blob or geometry data type, so you have to convert it to Text to use it later.  That text is probably formatted as JSON or some other format that can hold more than just the X,Y data of the object's shape,  so it has to be converted to a Dictionary (see below - generated by labeling simple test features with "line_geo" stolen from your first two lines of of code in your original post) we can see the dictionary contains an array called "paths" that stores the feature's coordinates.  So to reference that you have to pull it out of there...hence paths. Sort of makes sense.  I image its to keep Arcade on the "Simple" side.  To reference Geometry objects directly you would probably have to use something more like ArcObjects and object oriented programming...  .   ... View more