Latest Contributions by KristalWalsh

@KenBuja we have figured out the problem with my error, and I think I did not describe the workflow accurately. The intersect works just fine as we established above - a polygon [property] intersects the point [customer] which was placed first and the customer id is pulled into the property attribute. But if I select the customer point, say to add a new property, then choose edit from the pop-up, and then add a new feature, the relationship is broken or rather the customer id defaults to null and the script doesn't work as intended. The customer needs to be selected so that a 1:many relationship is maintained between customer:properties. At this time, I'm not sure what other workflow to use than to have ask the staff to place a point at every location where the customer has a property. Not ideal but at least this way I know the intersect will work and I can maintain a separate related table for all other customer info. If you have any thoughts, they would be greatly appreciated.

‎03-18-2024

There shouldn't be a time when there is no related record, unless of course, staff make a mistake somehow. I'm hoping to have that fool proof once I get this to EB. I've not done much work in EB but assuming I have to get everything functioning correctly here first. I double-checked the relationship class name and it's correct. I'm sure there's a breakdown somewhere on my end, just gotta find it. Thank you for your help.

‎03-18-2024

Thank you Ken, but it still fails to calculate the customer id value. I'm thinking the error has something to do with the fact that I am selecting an existing customer to edit and add a new related feature. Is the code missing a filter statement somewhere? I just don't know if that's the issue or if it matters.

‎03-15-2024

Hi, I'm not sure I'm even close with this script, so I'm hoping someone can help pull me through! The objective here is to intersect two features, pulling one id from one fc into another. The intersect part of the code works but when creating a second feature (per the form), as in a second property for an existing landowner, there is no intersect, so I just want the customer id from the related customer to be pulled into property fc. I know there's something missing, but I just don't know what or where to add it. Total Arcade novice here. // Define a Featureset (Customers) from the layer "Customers" in the $map // that contains the attribute ['CustomerID'] var Customers = FeatureSetByName($map, "Customers", ['CustomerID']) // Define a variable (code) to store the value we want // Get the value by Intersecting the polygon location // with the FeatureSet "Customers", or Customers var code = First(Intersects($feature, Customers)) // If the current location intersects Customers, // return the value in the field ['CustomerID']. // If no intersect, pull customer id into related feature layer [ProertyBoundary] var relcustid = First(FeatureSetByRelationshipName($feature.CustomerID, "Customers_PropertyBoundary")) if (!IsEmpty(code)) { return code['CustomerID'] } else { return Console(relcustid["CustomerID"])}

‎02-14-2024

@JohannesLindner hi, this is an old post but I'm attempting a similar attribute rule expression for a project in Pro. This data was brought in from an .mdb and the relationships have already been established on a UID that is not a Global ID. To create an attribute rule to push a calculation of table entries to a cell in the feature class, I established a global id field for the new .fgdb feature classes. 1) Is it okay to leave the relationships as they are? and 2) Do I need to add new GUID fields to the related tables? Thank you!

‎01-04-2024

Hi all, Happy New Year! I need to update an out of date .mdb with related tables to a fgdb for ArcGIS pro. Previous admins have used the object loader to append the new data (.shp) to the two feature classes in the existing .mdb. The new data is the same geometry and same projection as the existing data in the .mdb. I have no trouble updating one set of data but with the other data layer, I am getting the error "Table 'Delta_Layer name already exists". These two feature classes are ultimately related to each other. I'm not sure what is going on with this dataset and have even tried exporting the .shp to a fc but that doesn't work either. Does anyone have any ideas on resolving the error? I have to get the .mdb cleaned up before I can move it over to ArcGIS pro. My alternative for this one dataset is to use append, but I think I need to stick with the object loader for the other one which has many associated related tables. Thank you for your feedback!

‎11-06-2023

Thank you! I will check out the video but I was planning to populate a custom UID in addition to the system-generated Global ID/GUID and based on your filtering hint above, I think I will be able to make that happen with my custom ids. Paul Barker had helped me at the UC on a script to generate the sequence so I'm moving a little bit forward I think. Thank you so much! The feature-to-feature additions is also a huge step in the right direction. Have a great week.

‎11-02-2023

Hi @bbollin I read the blog and yes, I understand now how this will work. Thank you, it took me a couple days to get back to this. My decision to populate a UID other than the GlobalID generated from the relationship was based on the complexity of the GlobalID, need for a simple UID for everyday use and having a back up plan if we end up having to move this to the enterprise environment at some point. There are comments about the GlobalID/GUID relationships being compromised or lost during a move or export. Not being very good at scripting, any suggestion on a simple way to make this happen is appreciated. I know others must be using user-friendly ids with related tables but I haven't found any info on that yet. Thank you!

‎10-31-2023

I think I'm actually back to square one on ids honestly this has been the vain of my existence since the UC. You may be able to tell from the ERD attachment in the first post, that I have an auto-sequenced id (via Arcade and based on objectID +1) for the CustomerId field that is currently pulled into the PropertyBoundary layer through intersect. I need to be able to make sure that the property records (both feature layer and property info table) are matched to the correct customer. I thought auto-sequencing was the way to go and then using featuresets by relationship to pull that id into the property layer but it won't handle subsequent properties accurately. I'm not sure now how this should be set up. I do have the global and GUIDs set up for field maps but I wanted a user-friendly id to relate the customer to properties. I hope this makes sense.

‎10-31-2023

@bbollin so if I change my relationship back to feature to feature, and select the first feature of one hosted feature layer (customer), is there a way I can create a new feature from the related hosted feature layer (property boundary) based on the selection of the first feature? I think I'm seeing the need for Arcade here somewhere but not sure how this would work.

‎10-31-2023

No way!! LOL I haven't had time to check out the update because I've had my head buried in this. Man, this may be the 3rd time I've reconfigured this part of my workflow but better now than later. Thank you for bringing it to my attention!

‎10-31-2023

Currently customer info (point hosted feature layer) is entered, property boundaries created (polygon hosted FL) and the customer number (an auto-sequence id) is pulled by a spatial intersect in AGO. These two geometries are both related to the same propertyinfo table but was changed from a feature:feature relationship because this relationship type will not work in forms per this blog https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/introducing-related-record-editing-in-map-viewer/. My set up works okay for the first customer but I need to be able to maintain/ "pull" that customer id for subsequent properties that may be added for the same person? Creating additional customer points would duplicate customers and the auto-sequence arcade script renders the field not editable. I would like for the customer info to be found via search of the map, then a new property feature added. Without a feature-to-feature relationship, I'm not sure how to do this. This portion of the workflow does not have to be completed in Field Maps but needs to be user friendly, hence the forms. I've attached my scratchpad ERD. Thank you so much for any assistance!!

‎10-03-2023

@DougBrowning your input on this topic is very helpful. I think I mentioned I have been taking the traditional route with 1:1 and 1:many relates in a file geodatabase published to AGO and then forms designed in Field Maps, but having alot of errors and back and forth, also running into the fact it wouldn't handle feature to feature relates. So I'll be looking more into Survey 123 since I have only 5-6 tables. Hopefully it will be easier! Thank you!

‎10-03-2023

Thank you @TylerGraham2! I will be back on this project in the next couple days and really appreciate the help. I'm sure I will be back with an update. Hopefully it will be a success story.

‎09-28-2023

@TylerGraham2 could you please share your FieldMaps/Survey123 solution you mentioned above? It would be very helpful. Thank you!

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by KristalWalsh

Re: Calculated Expressions in Forms for Feature to Feature Relates

Re: Calculated Expressions in Forms for Feature to Feature Relates

Re: Calculated Expressions in Forms for Feature to Feature Relates

Calculated Expressions in Forms for Feature to Feature Relates

Re: Create Attribute Rule that populates a field in the feature class based on two conditions in the related inspection table.

Object loader error when updating .mdb

Re: One to many features with forms

Re: One to many features with forms

Re: One to many features with forms

Re: One to many features with forms

Re: One to many features with forms

One to many features with forms

Re: field map designer: related records not currently supported on mobile

Re: field map designer: related records not currently supported on mobile

Re: field map designer: related records not currently supported on mobile

Calculated Expressions in Forms for Feature to Fea...

Re: One to many features with forms

Re: One to many features with forms

One to many features with forms

Re: field map designer: related records not curren...