Field Maps URL - related table record - Specified layer couldn't be found

[KPyne]

Hello,

I am attempting to use a URL link to open up a related table record in Field Maps. I am using the following schema which all seems to be correct:

https://fieldmaps.arcgis.app/?referenceContext=updateFeature&itemID=d83642a09afb43a195d60418f3b0abf4...

However, it states "Unable to Update Feature - The specified layer couldn't be found"

The layer definitely exists, I am thinking related table records are not supported?

[ColinLawrence]

Hi @KPyne , updateFeature does not support opening directly to a table (related table). You would need to call the parent feature and then manually navigate to the record in question.

We did recently add the ability to add new related records via the addRelatedFeature parameter. 

[KPyne]

Bummer! Any chance "updateRelatedFeature" is in the works?

My use case is compliance inspections tied to an asset - wanted a URL link to quickly open the pending inspection and use the current related record functionality as a way to view historic records. (To save a few tap and because I cant seem to sort related records by date)

We generate new records in the backend once pending records are completed - otherwise addRelatedFeature would be great

[ahargreaves_FW]

@ColinLawrenceI fail to understand the difference between updateFeature (on a table) and addRelatedFeature. If i used the below I still get told "Unable to Add Feature - The specified layer couldn't be found" despite it being in the map, like the OP states:

https://fieldmaps.arcgis.app/?referenceContext=addRelatedFeature&itemID=86825f5cd0384151b67724efb6a1...

[ColinLawrence]

updateFeature is only intended for use in calling existing features, not table records. addRelatedFeature is used to add additional records to a child table in a related table. I am not sure if this is what you are asking, but there is no method to update an existing related record by using an app link. 

Looking at the URL you provide, I suspect it is going wrong at the foreignKeyField. This parameter should reference the key field from the parent layer. Also, ensure the featureSourceURL points to the URL to the parent layer as well. If there are multiple related tables for the parent layer, and they share the same key field, the app will choose the table with the lowest index number. 

I hope this helps clear things up!