POST
|
You need to create a related table in Pro then upload it to AGOL. The initial observation would be the base layer and subsequent observations would be in the related table. You can have a different form for each. Dan
... View more
4 weeks ago
|
0
|
0
|
352
|
POST
|
In the past, when I checked polygon areas on my map using the measurement tool in Map Viewer and compared that with what's shown in the attribute table, I noticed that the difference was some constant factor, i.e., the actual area in some units = the area in the attribute table in those units * K (where K is a constant). So I could just use the Calculate function on the attribute table to get the correct areas. This may not be the case today but it's worth checking. Dan
... View more
4 weeks ago
|
0
|
0
|
339
|
POST
|
We've discovered that in some cases ESRI changes stored dates/times in local time zone to GMT. This happened to us when we downloaded an attribute table as an Excel. You might check whether the incorrect dates/times actually are what you entered converted to GMT.
... View more
a month ago
|
2
|
0
|
393
|
POST
|
Chris, I think I solved the problem. As you suggested, just using Geometry($feature).x (or y) did work, which made me think that if I reduced the Arcade code I was using to a straight calculation maybe that would finish the job. Here's what I created to auto-populate Lat and Long fields: For latitude 57.2957795786 * (2.0 * Atan( Exp( (Geometry($feature).y * .00000898315285) * .0174532925)) - 1.570796325) For longitude Geometry($feature).x * .00000898315285 The results auto-fill the fields with decimal degree coordinates that match what the phone GPS shows as the location of the new point. I took all the arithmetic calculations in the original Arcade code and just replaced them with the number that resulted. This simplified the expressions a lot. Also, this reduces the multiple Arcade instructions I was using into a single calculated expression based solely on the Geometry functions which worked. Thanks for your help. Dan
... View more
08-09-2025
01:25 PM
|
0
|
1
|
311
|
POST
|
Chris, when I tried simply using "Geometry($feature).x" (or ".y") as you suggested, the fields were auto-populated with the Web Mercator coordinates. So you were correct that the problem is in the rest of the Arcade expression. But do you see what's wrong with it? You also suggested turning the conversion into a function. I don't know what that means or how to do it. Can you (or someone else in the community) provide more detail? Thanks again for your help. Dan
... View more
08-09-2025
06:44 AM
|
0
|
0
|
316
|
POST
|
Thanks, Chris, I'll try that. What does it mean to turn the conversion into a function? Dan
... View more
08-08-2025
01:54 PM
|
0
|
0
|
337
|
POST
|
Adrian, when I click "+" to add a new point, go through the filter associated with the layer, and then select "Add point", the point's lat and long in decimal degrees appear at the top of the FM form, presumably from the phone's GPS chip. Right now, I'm having field workers copy that info into the Lat and Long fields in the FM form. But FM should be able to auto-fill those fields. When I get the Web Mercator coords for the point that FM uses and run the Arcade formula shown in the post, I get the same decimal degrees as shown at the top of the form from the phone's GPS. I just can't get the result to auto-populate the two fields in the layer.
... View more
08-08-2025
08:51 AM
|
0
|
0
|
393
|
POST
|
When a new point is created in my editable layer, I want the lat/long in decimal degrees to auto-populate Latitude and Longitude fields (both double). The fields are not editable and show that they are calculated. But when I create a new point, these fields are not auto-populated. They just display "--". What are I doing wrong? Using latitude as an example, these fields are calculated using the Arcade expression below taken from the Forum. When I tested the expression, it gave me the result I expected, latitude in decimal degrees. Thanks for your help. Dan
... View more
08-08-2025
08:43 AM
|
0
|
7
|
397
|
POST
|
When I did as you suggested, it works! Thanks very much. Dan
... View more
06-30-2025
06:39 AM
|
0
|
0
|
361
|
POST
|
Thanks, I'll give that a try. What's the "rest service" for the table? Is it the detail you see when you View the URL? Dan
... View more
06-30-2025
06:18 AM
|
0
|
2
|
368
|
POST
|
Hello, all, I have a point layer ("Postfire_Planting_Data") that contains a field called Plot_ID and a related table ("Postfire_Monitoring_Data_Related") (1:M) that records updates to the original point. I'd like to auto-populate a Plot_ID field in the related table form using the Plot_ID from the parent layer. The layer and table are related via GlobalID (layer) to GUID (table). The ArcPro project GDB calls the relationship "Postfire_Planting_Data_Postfire_Monitoring_Data_Related". The layer, table, and relationship class were uploaded to AGOL, and I used FM Designer to create forms for the parent layer and the related table. The Plot_ID field in the parent layer always is filled in. I want to pull that ID from the parent layer into every related table entry associated with a point in the parent layer. I saw a number of variations of Arcade coding that supposedly would do this, but none have worked for me. Here's my last attempt, which tests in FM Designer to return "null" but on the FM app related table form says it can't calculate a value. var parent_features = FeatureSetByRelationshipName ($feature, 'Postfire_Planting_Data_Postfire_Monitoring_Data_Related', ['Plot_ID']); var parent_feature = First(parent_features); if (!IsEmpty (parent_feature)) {return parent_feature ['Plot_ID']} else {return null} Since the Plot_ID field in the parent layer always is filled in, I tried replacing the 2nd and 3rd Arcade lines above with just "return parent_features ['Plot_ID']", but that didn't work either. Surely this is a common problem with an obvious solution. I just can't find one that works! Any help would be appreciated. Thank you, Dan Gruber
... View more
06-29-2025
09:37 PM
|
0
|
4
|
429
|
POST
|
Lindsay, I see that there is a template correpsonding to the field I'm using for map symbology. The list that appears below the "Filter" bar contains the options for that field. I have to select one of the list items to continue to the form, and that field in the form is filled out with the item I clicked on (although I can change it once in the form itself). I don't want the search bar to appear at all, i.e., I want to go directly to the form when I add a new point to the layer with none of the fields prefilled. Can I just delete the template? Would the template/search bar go away if I reverted to single symbol symbology based just on the location of existing points? Thanks for your help! Dan
... View more
06-16-2025
07:07 AM
|
0
|
1
|
361
|
POST
|
I created a map with a layer and a related table, and then used Designer to create forms for both the layer and the table. When I want to add a new point to the layer in the FM app on my phone, it starts with a filter for one particular field in the layer. In Designer, filters are set to "Off" and I don't want to use any filters when adding a new point to the layer. Why am I getting a filter when filtering is "Off" in Designer, and how do I get rid of the unwanted filter that's showing up? Thanks for your help. Dan Gruber
... View more
06-15-2025
02:22 PM
|
0
|
3
|
502
|
POST
|
We routinely use related tables in FM. The key is to use FM Designer to create a form for the related table, not the base layer. In the field, our people click on the appropriate point/poly on the map - which is the base layer - and then use the link icon to access the related records and add a new entry. Works fine.
... View more
11-13-2024
12:09 PM
|
0
|
0
|
941
|
POST
|
Create a related table in Pro and then upload it to AGOL and FM. New entries are added to the related table, and all are associated with one original point. We routinely use this approach to record repeat visits to the same locations. See https://www.youtube.com/watch?app=desktop&v=Fo9tP9qkm8k for easy instructions about creating a related table in Pro.
... View more
11-09-2024
06:04 AM
|
0
|
0
|
980
|
Title | Kudos | Posted |
---|---|---|
2 | a month ago | |
1 | 07-18-2024 08:04 AM | |
1 | 05-24-2023 04:12 PM | |
2 | 02-23-2024 06:14 AM | |
5 | 06-13-2023 10:16 AM |
Online Status |
Offline
|
Date Last Visited |
a month ago
|