Latest Contributions by AmirBar-Maor

Hi @RuthWorkman  We've added new geoprocessing (GP) tools in 3.2  GP Delete Parcels: 3.2 GP Create Parcel Seeds: 3.2 Activate record - can be done using a python script: 3.2 GP Export Parcel Record Features: 3.2 GP Select Parcel Features: 3.3 GP Duplicate Parcels: 3.3 As for the Merge tool, and any other tool exposed on the REST API, those can be accessed using the python arcgis library - see documentation here. So I am thinking of marking this as 'implemented' for 3.3 and asking you (and others) to submit any specific tools that make sense to implement. Does this make sense? ... View more

@Wade_Cherry  Thanks @AliciaTompkins for sharing the BUGs you have logged. They occur with ArcGIS Pro 3.2 and when using feature services. We are working to fix them in ArcGIS pro 3.3 and intend to patch 3.2 with those fixes. ... View more

Another idea to consider without writing any scripts is using attribute Rules. They will not honor selection so they could be used when: The attributes being updated can be copied from another feature they intersect Or, they can be copied between the tables based on an attributes that links them together (can be used in a SQL query to 'Filter()' the 'feature Set'.   If this is a repeatable workflow, tasks can also be used to copy attributes from one feature and apply them to features that you select, or features that are created or modified during the task. ... View more

@TroyIngold  Did you try to configure the User Interface option to increase the 'User Interface scaling?   If you increase it to 200% (which is likely too much) this is what you get:       ... View more

@AdamHart1  Thanks for providing the data. In order to copy data from the CAMA table to the Records table we'll need a unique value in both tables. In the CAMA table you want to use a field called 'ParcelNumber' which contains an APN (PIN) The record name is "Lincoln_Merge_2024_22652" (Name field) - I would expect the record name to be used to link the 2 tables. The fields 'Created Parcel Count' and 'Retired Parcel Count' in the records table store the number of parcels that the record created and retired, and not a unique value. Once we find a the field that has a unique value in both tables, the Attribute Rule can copy any field from CAMA to the records table. Can you please clarify?         ... View more

@AndrewWallick  It looks like your script is failing on the first line... It might be a good time to contact technical support to have a look. For example - maybe the version of your enterprise is too old?! Do you use the fully qualified relationship name? for example in this case the relationship class name is 'cadastre.amir.RecordHasTax_4' Did you check the 'Exclude from client evaluation' checkbox on your rule? ...         ... View more

@AndrewWallick  Please disregard my last comment.  I have modified the expression to this: var Record = First(FeatureSetByRelationshipName($feature, 'RecordHasTax', ['Name'], false)); If (IsEmpty(Record)) { return "No Record Found"; } return Record.Name;   It checks to make sure the relationship is not empty. You can see that the popup and Attribute Pane show the same result:   And if it's empty: Let me know if this now works for you     ... View more

@AndrewWallick  Absolutely! To populate the name of the record that CREATED the parcel it's exactly the same expression. For the retired record there are 2 options: Create a relationship class using the RetiredByRecord field and then use that relationship class in your expression (same expression) Use a SQL expression and the Arcade command 'Filter' to get the record. Let me know if you would like me to provide you with the expression for this option. Should only take a few minutes to create and test. ... View more

@AdamHart1  Great to see integration to the CAMA data. All the variables in your expression are 'Feature Sets' - those are collections of features. You also have variables that are not used. I can help you with the expression if you can share a small portion of the data. If the data is sensitive you can  export an empty schema as XML Workspace and then import it to a new file geodatabase, add a couple of rows manually with the data you want to see copied over. ... View more

@MizukiKayano2  From my understanding, your organization decided to combine the historic parcels and current parcels into a single layer.  Is it possible that we are trying to solve a problem that can be easily prevented by working with the default layers (separate layers for historic and current)? ... View more