https://community.esri.com/t5/attribute-rules-questions/pull-data-from-another-table-based-on-text-entry/m-p/1516241#M1530 <P>Hi,</P><P>Have a set of Attribute Rules (AR) set up for calculating data and for pulling data from an intersecting table.&nbsp; Placing a point and grabbing the PID, area, and a few other columns from the Parcel table.&nbsp; Using Intersects in the AR.&nbsp; However, our parcel table has overlapping polygons for condos and leaseholds.&nbsp; When the point is placed on a single parcel the First(Intersects(feature)) works absolutely great.&nbsp; However, on these condos/leases, it returns the first one and that is not always the proper parcel to be returning.&nbsp; 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.</P><P>I'm wondering if anyone has run into this before and how you may have solved it.&nbsp; 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).&nbsp;&nbsp;</P><P>I'm thinking of a few ideas.</P><P>One, remove the First from the Intersects function, but get a count of how many intersections there are.&nbsp; If equal to 1, then proceed with getting the attributes and populating as normal.&nbsp; 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!</P><P>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.</P><P>Thanks,</P><P>Lorinda</P> Wed, 07 Aug 2024 17:42:45 GMT LorindaGilbert 2024-08-07T17:42:45Z https://community.esri.com/t5/attribute-rules-questions/pull-data-from-another-table-based-on-text-entry/m-p/1516241#M1530 <P>Hi,</P><P>Have a set of Attribute Rules (AR) set up for calculating data and for pulling data from an intersecting table.&nbsp; Placing a point and grabbing the PID, area, and a few other columns from the Parcel table.&nbsp; Using Intersects in the AR.&nbsp; However, our parcel table has overlapping polygons for condos and leaseholds.&nbsp; When the point is placed on a single parcel the First(Intersects(feature)) works absolutely great.&nbsp; However, on these condos/leases, it returns the first one and that is not always the proper parcel to be returning.&nbsp; 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.</P><P>I'm wondering if anyone has run into this before and how you may have solved it.&nbsp; 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).&nbsp;&nbsp;</P><P>I'm thinking of a few ideas.</P><P>One, remove the First from the Intersects function, but get a count of how many intersections there are.&nbsp; If equal to 1, then proceed with getting the attributes and populating as normal.&nbsp; 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!</P><P>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.</P><P>Thanks,</P><P>Lorinda</P> Wed, 07 Aug 2024 17:42:45 GMT https://community.esri.com/t5/attribute-rules-questions/pull-data-from-another-table-based-on-text-entry/m-p/1516241#M1530 LorindaGilbert 2024-08-07T17:42:45Z https://community.esri.com/t5/attribute-rules-questions/pull-data-from-another-table-based-on-text-entry/m-p/1520867#M1535 <P>JohannesLinder or JoeBorgione, have either of you run into this type of scenario?</P><P>Thanks,</P><P>Lorinda</P> Tue, 13 Aug 2024 21:24:17 GMT https://community.esri.com/t5/attribute-rules-questions/pull-data-from-another-table-based-on-text-entry/m-p/1520867#M1535 LorindaGilbert 2024-08-13T21:24:17Z