topic Re: field map designer: related records not currently supported on mobile in ArcGIS Field Maps Questions

field map designer: related records not currently supported on mobile

L77 — Wed, 28 Jun 2023 18:24:25 GMT

My coworker is getting this error:

Related Records not currently supported on mobile.

It is my role to help her troubleshoot when she has issues. How do I know if there is an issue with her data or the field map designer tool?

In field maps she can see the related table and can edit it and the edits are syncing to her online map.

But she can't view or modify the related table in the field map designer tool. She said that it was working this morning.

I had her create a new map that only had the point layer with the related table and open it in field maps designer and it had the same error.

I'm not sure what to try next. I told her that maybe there is an issue with the tool and to wait an hour and check again then to see if it is resolved.

If you have any troubleshooting suggestions please let me know.

Also, does anyone know if there is a place where I can read about current bugs with field maps designer or field maps mobile app? We are using these tools daily now so it would be nice to look for bugs so we will know if there is something wrong with our data or something wrong with our tools.

Thank you!

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

L77 — Thu, 29 Jun 2023 16:22:00 GMT

We just figured it out.

When she opened the map in Field Map Designer, she dragged the related table into the form for the point dataset that it was related to thinking that this would be necessary for the related records to show up in the form.

But this wasn't necessary to get the related table to show up in field maps, it was kind of like a redundancy that showed the error message.

As soon as she removed the related table from the form of the point layer the error message went away.

She tested it in field maps and was able to see the related records in her point layers form.

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

MSFIVolunteers1 — Sun, 23 Jul 2023 20:53:28 GMT

Please elaborate. I see the same error. I created a layer with a related table in Pro and published it onto an AGOL map. Then I opened the map in FM Designer. The layer shows under "Layers" in the "Forms" section on the left and can be configured, and the related table is shown under "Tables" in the "Forms" area on the left and also can be configured. What am I doing wrong?

Thanks.

Dan

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

Gisbert61 — Mon, 21 Aug 2023 13:37:15 GMT

Same error here, I have an existing hosted feature class with related table and on opening the field maps designer, choosing the map and the feature layer this error occurs.

By the way; i created a new and empty feature class and related table as per (https://support.esri.com/en-us/knowledge-base/how-to-set-up-related-tables-in-arcgis-pro-for-use-in-a-000028010) and published this to my online. After opening the field maps designer, you guessed it: same unwanted error.

How now ESRI? what 'm I doing wrong this time? Where can I find a walk-through, clear instructions? This is frustrating as my field people desparately need a simple and clean inspections app.

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

DougBrowning — Wed, 23 Aug 2023 17:06:58 GMT

Same issue here. Add all is greyed out for some reason. Can not add any related records at all now. I do not have any related table fields in my form. Started an all new map and form and still no. Totally stuck now.

Checked to make sure I meet all requirements detailed here https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/introducing-related-record-editing-in-map-viewer/

thanks

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

DougBrowning — Thu, 24 Aug 2023 19:56:31 GMT

I think I figured mine out at least. You must go through the Forms Designer from Map Viewer then it will let me add the related. While you can use Field Maps Designer to design forms and Map Viewer picks up those forms the options in Field Maps Designer are slightly different. They seemed to be interchangeable but they are not. They both look and act the same.

Hope that helps someone.

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

TylerGraham2 — Thu, 07 Sep 2023 21:56:38 GMT

This solution worked for me too, eventually. I had the "Related Records not currently supported on mobile" message when accessing the Forms Builder through both Field Maps Designer and (after I saw your suggestion) Map Viewer. Then if I tried entering data in Field Maps, the feature layer worked fine, but I would get an "unable to submit 1 or more attributes failed" message if I tried to enter data in the related table. My table has relationships with several different feature layers that all pointed to the same GUID in the table. I had to make a GUID field in the table for each feature layer to relate to independently, reestablish the relations and then republish. After that, when I access Forms Builder through Map Viewer, the Related Records message doesn't appear.

I'm throwing my solution here because my problem became apparent in Field Maps Designer with the same message OP had and I'd like to save others who may have a similar problem some time. It is a separate issue and the solution is documented in this bug report, but I couldn't find the resolution to it when looking for the "Related Records not currently supported on mobile" message.

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

KristalWalsh — Tue, 26 Sep 2023 18:39:00 GMT

This is interesting, @TylerGraham2 because I have the same relational db design with feature layers pointing to the same table. However, I also have more than one table relate for two of my feature layers. I haven't been able to find anything yet about whether Field Maps designer will accommodate anything like this. Can you or @DougBrowning comment? I'm building in Pro, publishing to AGO and have gone back and forth several times already to change up my approach. I appreciate your posts!

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

DougBrowning — Tue, 26 Sep 2023 18:51:10 GMT

In order to use the related feature you cannot use Field Maps designer is what I found. You have to go to the form designer from the map only.

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

KristalWalsh — Tue, 26 Sep 2023 18:56:17 GMT

Okay, got it. I'm still in the process rebuilding a couple tables, but do you know if more than one table relate per feature layer will work in the map viewer? I think I may have to use groups or logic to keep the fields from opening all at once if it will work. Thank you!

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

TylerGraham2 — Tue, 26 Sep 2023 19:40:15 GMT

Here's my schema with relates as the lines. The point/line/polygon features are all a 1:1 relate to the monitoring notes and the tables under the monitoring notes are all 1:many. The related records will show in the pop-ups under their appropriate tables, but I don't think you can add them to the forms for data collection yet.

My setup that I'm currently testing is to enter the point/line/polygon data in Field Maps, then you open the pop-up for that feature and tap a link that launches Survey123 with a blank survey if there is no related monitoring note record or if it finds one, it opens it for editing. The tables related to monitoring notes are all handled as repeats in Survey123.

If you go that route, the related tables aliases cannot have spaces or other special characters not allowed in the Survey123 Connect xlsx 'name' column. When you publish a hosted feature service in Pro 3.1, it uses the aliases of feature classes and tables as the name of the hosted feature layers and tables. So for example "Monitoring Notes" should have the alias as something like "MonitoringNotes" or "Monitoring_Notes".

There's also an issue with Field Maps and Arcade for passing q:queryparameters to the custom URL schema to find matching records from Integrate with other apps. The query has to be formatted a very particular way and passing it through UrlEncode() will mess it up. I appended the query for the global id after encoding the rest of the URL, which worked with web maps. Field Maps however would generate the URL with everything in the query except the global id value. It will only pass it through UrlEncode(). I've got a solution that I figured out yesterday. It works well and Esri tech support liked it too. If you're interested in pursuing Field Maps/Survey123 integration let me know and I'll be happy to share it.

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

DougBrowning — Tue, 26 Sep 2023 20:34:20 GMT

It seems to list them all yes. My names just look blank since 123 has been creating relationship classes with no name still, which I hope they fix some day. Note only related tables are given as options since still no support for related layers. Which is weird tables usually come last.

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

KristalWalsh — Tue, 26 Sep 2023 21:10:41 GMT

Thanks for posting your schema diagram and the part about the aliases. I'm a bit confused about "The related records will show in the pop-ups under their appropriate tables, but I don't think you can add them to the forms for data collection yet." I've added related records to the form in the map viewer but I haven't gotten to the testing phase in field maps yet. So this is a new one. 😞 My schema diagram is much more complicated with many 1:many relates so this all just tells me I need to start small and take it all the way through to Field Maps to see what's gonna work. I also have not thought about using Survey 123 because of the 1:many relates. I would welcome the solution on Field Maps/Survey123. I may be headed back to the drawing board on this.

This has been working on a much smaller scale for one region of Florida but was built before form designer or the new map viewer etc. etc. and it worked great in Field Maps. Oh well. Thank you so much.

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

TylerGraham2 — Tue, 26 Sep 2023 22:49:18 GMT

@DougBrowning If you go to the REST admin page for the feature layers/tables it will show the relationship names there if you need it for arcade expressions. I have some feature services published through Connect with repeat tables and it shows a relationship name for each of those. The relationship name excludes the number in () after the name. So if you have a relationship named like Dougs_GIS_table_chairs (1) and wanted to test it with FeatureSetByRelationshipName() you would enter 'Dougs_GIS_table_chairs' for the relationship name.

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

KristalWalsh — Thu, 28 Sep 2023 19:36:46 GMT

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

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

TylerGraham2 — Tue, 03 Oct 2023 13:48:19 GMT

@KristalWalsh

Here you go. This will create a link in a pop-up to open the survey record from the inbox in edit mode.

var urlsource = 'arcgis-survey123://?';
//Custom URL Schema
var item_id = <Survey's ItemID fround on Survey123 website>;
//form item ID, found by going to survey123.arcgis.com and copying from the survey link under collaborate
var guid_field = <guid field name>;
// GUID field in related table, foreign key points back to feature layer

var globalid = $feature.GlobalID;
//pull individual feature's globalid value
var q_exp = guid_field + "='" + globalid +"'";
//query expression to search survey table for guid that matches feature global id, must be passed in UrlEncode()
var linktext = <Put link display text here>;

var params = {
//parameters for UrlEncode()
action: 'edit',
//sets survey123 to edit existing record
folder: 'inbox',
//searches the survey123 inbox
itemID: item_id,
//use form item id here to target specified survey
update: 'true',
"q:where": q_exp
//for query parameters to work in URL encode must be "q:where": to pass the query into the link as q%3Awhere=
//if the '=' after the where is encoded as html the query fails because it doesn't know how to recognize the html encode
//the field name has to be specifically typed here, if it is assigned as a variable elsewhere in the expression and the
//variable is called here it includes the variable name along with the variable and causes the expression to fail.
};

var fullURL = Concatenate([urlsource,UrlEncode(params)]);
//creates the full dynamic url
return {
type: 'text',
text: `<p> <a href="${fullURL}" target="_blank">${linktext}</a></p>`,
//this property supports html tags
};

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

DougBrowning — Tue, 03 Oct 2023 13:58:39 GMT

I have a write up on using related layers and tables with 123 and Field Maps here also https://community.esri.com/t5/arcgis-survey123-questions/mapping-with-survey123-within-a-polygon-or-admin/td-p/836112

If you have several forms it is a great workflow. Field Maps is good at spatial to get the crew to the correct sport. 123 is good at forms so we launch all 15 forms from Field Maps pushing over the Key and other config variables. Then they all link together using relationships classes. Then I have a call back that flips them back to Field Maps on a save. Works slick.

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

KristalWalsh — Tue, 03 Oct 2023 21:16:52 GMT

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.

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

KristalWalsh — Tue, 03 Oct 2023 21:22:15 GMT

@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!

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

tiztrain — Thu, 02 Nov 2023 09:24:52 GMT

Does Field Maps work with multiple relationships? If it does, do you just need to create a GUID field for every table that has the cardinality of 'Many'?