Hi,
Have a set of Attribute Rules (AR) set up for calculating data and for pulling data from an intersecting table. Placing a point and grabbing the PID, area, and a few other columns from the Parcel table. Using Intersects in the AR. However, our parcel table has overlapping polygons for condos and leaseholds. When the point is placed on a single parcel the First(Intersects(feature)) works absolutely great. However, on these condos/leases, it returns the first one and that is not always the proper parcel to be returning. We are wanting to keep these fields as non-editable so as to reduce chance of error in the data since there are related tables to at least one of the fields.
I'm wondering if anyone has run into this before and how you may have solved it. I have a couple of ideas, but am not sure what the syntax is (a search of the functions, etc in arcade has been fruitless right now, will continue to search).
I'm thinking of a few ideas.
One, remove the First from the Intersects function, but get a count of how many intersections there are. If equal to 1, then proceed with getting the attributes and populating as normal. If greater than 1, could a text entry field be popped up to have a portion of the parcel id entered and then use 'sql' queries to populate the data? Or is there a list function that would allow for a selection to be made from a list - this is likely to be the least desirable as we have some condos with over 250 units, and that is a lot of scrolling and easy to miss the one desired!
Two, other idea that I have is to have the parcel id entered by the user, then using that entry, do a 'sql' query to populate the fields in the table - at this point it would likely be better to use a dictionary as there are four or five fields coming from the parcel table.
Thanks,
Lorinda
