nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Copying Records in Field Maps

marksm_macomb

I created a new Field Map for doing stormwater inspections that is very similar to a Field Map I had already put together for sanitary inspections. On both field maps the inspection records are related to the parent features via GUID, the only difference is that the stormwater inspections have 5 related assets (there are many different types of storm features that get the same inspection) while the sanitary manholes only have 1 related asset (only manholes are inspected).

With the sanitary manhole inspections, our team has been opening the previous inspection record in Field Maps and making a copy of it since not a lot changes from inspection to inspection and it saves them a lot of time. This has worked well for us.

But as I'm setting up the stormwater inspection map, for some reason I am not seeing the Copy button like I do in the sanitary map. I have double checked that all their editing settings look the same, and I tried following the advice in this thread to uncheck and re-check copy settings in Field Maps Designer: Copy Features not availabe for certain feature classes in Field Maps

Has anyone else run into this issue? Could it be related to the relationship classes? Photos included to show what Copy button I am referring to:

Sanitary Inspection with Copy Button Storm Inspection without Copy Button

Thank you!

Encontre mais publicações marcadas com

Accepted answers

marksm_macomb

Thank you for sharing! I do have the relationships set up similarly (with individual GUIDs) but I don't have the relGlobalID or sourceFC fields.

With some more trial and error, I figured out something interesting. I had noticed that ONE of my asset types would allow me to copy related records, while the other 4 would not. That one asset was the only one that I did not have duplicate layers of in my Field Map. I have duplicate layers for the other assets in order to do some more involved symbology (highlighting certain assets as needing attention, etc). When I removed those duplicate layers, I was able to copy the related records on those assets. Weird! I will have to now figure out a work around for my symbology.

All comments

RhettZufelt

Do each of your storm assets have their own related table, or are you using one table for all of them?

Not sure if it's related, but I had several issues going from my Sewer inspection app to my Storm inspection app because of the multiple asset types and using a single table for all of my storm inspections, even though the GUID is unique.

Easiest fix was to have a separate storm inspection table for each of the storm assets.

However, for local reasons, we wanted all the storm inspections in one table, regardless of asset type.

Once I created a separate GUID field for each of the assets in the storm tracking table, then set up a relationship class on each asset pointing to its specific GUID field in the inspections table, all the weird relationship confusion went away.

Just tested it and I do see and am able to copy previous inspections.

Hope this helps,

marksm_macomb

@RhettZufelt

Thanks for the reply. I also want all the storm inspection information in one table. When I first created the storm inspection table, I just made the relationship with a single ParentGUID field, and noticed some other weird things happening, then I figured out to make each asset have its own ParentGUID field. I deleted the old relationship, created the new relationships using individual GUIDS, and overwrote the layer. I wonder if I just need to start from scratch and redo it in case there's any hidden junk from the old relationship in there 😕

marksm_macomb

Would you mind sharing a screenshot of your schema or relationship class set up to ensure I'm following the same pattern? I just found this bug which could explain why there are issues: BUG-000179417 for ArcGIS Field Maps

RhettZufelt

Sure, but I don't think I have that bug issue as I still only have one relationship class on each featureclass.
Also, to clarify, I am running this on Enterprise 10.9.1 with registered feature services on SQL server database.
The relationship classes were setup on the data, then published to Enterprise portal with ArcGIS Pro.

Showing relationship class between Manholes FC and StormTrackingTable (Inspections table).

Showing relationship class between Inlets FC and StormTrackingTable (Inspections table).

Plus I have relationship classes set up on all the other FC's to be inspected, but these two should give the idea.

Here are the relevant fields in the Inspections table:

and a snippet of part of that table:

So, a Manhole inspection puts the relative Manhole GlobalID into the ManholeGUID field, Inlets into the InletGUID field, etc. I also populate the RelGlolabID field with the same feature GlobalID, along with the SourceFC field of the FC being inspected. This makes it much easier in processing to be able to just query by SourceFC and GUID when needed.

Then, in FMA, select Manhole with existing Inspection, select one of the inspections and :

marksm_macomb

Thank you for sharing! I do have the relationships set up similarly (with individual GUIDs) but I don't have the relGlobalID or sourceFC fields.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.