|
POST
|
Thank you! I did not notice that, or know that %20 corresponded with a space. I appreciate the help. I do think a blog or something on this would be helpful for others though.
... View more
02-04-2022
05:26 AM
|
1
|
2
|
9599
|
|
POST
|
@Anonymous User - This is the encoded URL I am using - Survey123 launches from Field Maps just fine, but the callback doesn't happen. I submit the Survey and am returned to the Survey123 home instead of Field Maps. Any advice would be useful. arcgis-survey123://?portalUrl=https://www.arcgis.com&itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID}&callback=https%3A%2F%2Ffieldmaps.arcgis.app%20%2F%3FreferenceContext%3Dopen%26itemID%3D6b34dffb1c0b41b3907c61a97d0b1e4a Thank you,
... View more
02-03-2022
12:18 PM
|
0
|
5
|
9608
|
|
POST
|
Hi @Anonymous User - I will test this to see if it fixes my issue. If this is the recommended way of doing this, I would recommend an update to the documentation available on the Field Maps and Survey123 help pages because it is not clear at all. Thank you,
... View more
02-02-2022
09:44 AM
|
0
|
0
|
9624
|
|
POST
|
Hi - I am migrating some workflows from Collector to Field Maps and I am running into issues with my callback URL parameters. The workflow: Click a polygon feature in Field Maps to view pop-up. Custom pop-up displays URL to launch Survey123 form and pass certain attributes to Survey123. Survey is completed by user. When user submits survey, Field Maps re-opens via callback to specified map. This worked very well with Collector and was simple to configure. With Field Maps, I am getting some weird errors, even though I am following the documentation on both Survey123 and Field Maps help pages. If I use a URL formatted like below, I get an error when attempting to open Survey123 from the URL. The error is in Survey123 and says "Error Unpacking": https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID }&callback=https://fieldmaps.arcgis.app /?referenceContext=open&itemID=6b34dffb1c0b41b3907c61a97d0b1e4a This same error occurs when I modified the URL to be something like this: https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID}&callback=https://fieldmaps.arcgis.app://?referenceContext=open&itemID=6b34dffb1c0b41b3907c61a97d0b1e4a https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID}&callback=https://fieldmaps.arcgis.app//?referenceContext=open&itemID=6b34dffb1c0b41b3907c61a97d0b1e4a If I use the callback URL without the referenceContext parameter included, the callback seems to work, but does display an on-screen error when returning to Field Maps; this happens with either of the formats below: https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID }&callback=https://fieldmaps.arcgis.app ://?itemID=6b34dffb1c0b41b3907c61a97d0b1e4a https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID }&callback=https://fieldmaps.arcgis.app /?itemID=6b34dffb1c0b41b3907c61a97d0b1e4a Error: I did check and the Survey123 data submits properly. I am returned to the proper map in Field Maps, but see this error each time. Does anyone have advice on how to resolve this issue? Thank you,
... View more
02-01-2022
05:39 AM
|
0
|
14
|
11796
|
|
POST
|
Hi - I am migrating some workflows from Collector to Field Maps and I am running into issues with my callback URL parameters. The workflow: Click a polygon feature in Field Maps to view pop-up. Custom pop-up displays URL to launch Survey123 form and pass certain attributes to Survey123. Survey is completed by user. When user submits survey, Field Maps re-opens via callback to specified map. This worked very well with Collector and was simple to configure. With Field Maps, I am getting some weird errors, even though I am following the documentation on both Survey123 and Field Maps help pages. If I use a URL formatted like below, I get an error when attempting to open Survey123 from the URL. The error is in Survey123 and says "Error Unpacking": https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID }&callback=https://fieldmaps.arcgis.app /?referenceContext=open&itemID=6b34dffb1c0b41b3907c61a97d0b1e4a This same error occurs when I modified the URL to be something like this: https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID}&callback=https://fieldmaps.arcgis.app://?referenceContext=open&itemID=6b34dffb1c0b41b3907c61a97d0b1e4a https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID}&callback=https://fieldmaps.arcgis.app//?referenceContext=open&itemID=6b34dffb1c0b41b3907c61a97d0b1e4a If I use the callback URL without the referenceContext parameter included, the callback seems to work, but does display an on-screen error when returning to Field Maps; this happens with either of the formats below: https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID }&callback=https://fieldmaps.arcgis.app ://?itemID=6b34dffb1c0b41b3907c61a97d0b1e4a https://survey123.arcgis.app/?itemID=10242016ba5b4ab3883bf40bb8ae76fb&field:Ag_Guid={GlobalID }&callback=https://fieldmaps.arcgis.app /?itemID=6b34dffb1c0b41b3907c61a97d0b1e4a Error: I did check and the Survey123 data submits properly. I am returned to the proper map in Field Maps, but see this error each time. Does anyone have advice on how to resolve this issue? Thank you,
... View more
01-31-2022
07:23 AM
|
1
|
2
|
4322
|
|
IDEA
|
@Anonymous User - I am so used to the way Survey123 deals with this that it is really not an issue to me anymore as Survey123 is my agencies primary method of field data collection. That being said...anything that can be done to improve the experience in Field Maps would be welcome. I would only wonder for those workflows that might be migrated from Survey123 to Field Maps (if select multiple became available and the stored value method was different from how Survey123 does it), how would the data be affected? It seems content managers would need to do some work to fix things in the table.
... View more
01-06-2022
05:22 AM
|
0
|
0
|
5785
|
|
BLOG
|
@GlenShepherd @DerekMStrout - I would be very interested in learning more about that setting and how it can be used/affects Overwrite operations where View layers are in use. Also, @GlenShepherd - have there been any updates on the Esri end with regard to the broken/disconnected View issue I had posted questions about back in August 2021? I know some of the View experience was enhanced with the last release of AGOL, but I do not think this was addressed. Thank you!
... View more
01-05-2022
05:55 AM
|
0
|
0
|
16099
|
|
IDEA
|
@Anonymous User - Hoping to chime in here with some answers to your questions as this is something we'd also love to see implemented in Field Maps. If this was added, we'd be able to simplify some field workflows by removing the Survey123 component (which is used if we need to select multiple values). Survey123 implements this as a comma delimited list of values stored in a string field. This can make it difficult to re-use in other areas of ArcGIS. For those of you who use Survey123: How do you use the captured data for these fields? Do you show the layers in other apps/maps besides Survey123? Yes - we generally display collected data in Dashboards. Do you use hidden fields & calculations to split the choices into separate fields? No - we store the data as comma delimited and then work with it later using Arcade Data Expressions or something like R. Do you use Arcade in Pop-ups and Dashboards to format the data? Yes - we use Data Expressions in Dashboards to break the data out for charts. Would you expect to be able to create a multiple choice element for existing fields? Primarily this would be used to migrate existing (simple) workflows from Survey123 to Field Maps. We have existing domain values assigned already and would like to just "check off" a select multiple option to allow for multiple choices to be selected. Similar to the experience when building a Survey123 form in Connect "on top" of an existing feature layer. If so, do those fields have existing coded value domains? Are they string fields or integer fields? Yes to existing coded value domains - both string and integer fields, however string is much more common. Would it be beneficial to have a multiple choice UI/UX that stores each choice in a separate "boolean" field instead of a comma delimited list? I'd be interested to see how this would affect schema design. It sounds nice, but with the capabilities of Data Expressions, I am unsure if I'd give a hard and fast "yes" here without knowing more about how the schema is affected for existing data layers. How many choices per question are anticipated? I'd agree with @RogerCleaves1 that ~20 choices would be adequate when thinking of my existing workflows that I'd like to migrate. Would you need to add or remove choices over time? Potentially. If so, should that affect previously collected data? No - if a choice is added or removed, all existing data with that value should not be changed. Would you need to deprecate choices over time? Potentially - same response as above. Would you need to edit an existing choice name/values? Ideally not, but it is always possible. If so, should that affect previously collected data? It would be nice, but this can also be dealt with via Pro. Do the choices needs any additional information displayed with them, like a description? Or is the value/name enough? It would be ideal, in my opinion, to have a similar set up to Survey123 where you have the stored code and the label that is shown to the user in the application. If so, can you provide a specific example? We have coded values for our subbasins - 5 = Ball Brook. We don't want a list of numbers to show up for users, we want the list of labels that correspond. Another example would be for stream codes - the description is much more useful for field staff.
... View more
01-05-2022
05:39 AM
|
0
|
0
|
15557
|
|
BLOG
|
I am curious how or if this takes into account the orientation of the device - portrait vs landscape. This may be a totally different scenario from this new appearance, however I am curious because we had done testing a few years ago in regards to the internal device compass direction that is captured in a photo's EXIF data. What we found was that if we wanted users to take landscape-oriented photos, they needed to be consistent about how they did this. We instruct users to always take landscape oriented photos with the "home button" (bottom of device) in their right hand. Then, we were able to accurately calculate the compass direction within a report template based on that known orientation of the device at the time of capturing the photo. Would a similar sort of calculation need to take place within the survey form for this type of question depending on how users are holding their device when completing their survey? We use this calculation within a report template to determine the actual compass direction that the photo is facing from photo EXIF data. Again, maybe this is different because it is relating to a photo/EXIF data/report templates, but I thought this was worth asking. ${if (((Related_Table_Photo_Information.Image | getValue:“direction”)>=0.0) && ((Related_Table_Photo_Information.Image | getValue:“direction”)<=22.4))} E ${/}${if (((Related_Table_Photo_Information.Image | getValue:“direction”)>=22.5) && ((Related_Table_Photo_Information.Image | getValue:“direction”)<=67.4))} SE ${/}${if (((Related_Table_Photo_Information.Image | getValue:“direction”)>=67.5) && ((Related_Table_Photo_Information.Image | getValue:“direction”)<=112.4))} S ${/}${if (((Related_Table_Photo_Information.Image | getValue:“direction”)>=112.5) && ((Related_Table_Photo_Information.Image | getValue:“direction”)<=157.4))} SW ${/}${if (((Related_Table_Photo_Information.Image | getValue:“direction”)>=157.5) && ((Related_Table_Photo_Information.Image | getValue:“direction”)<=202.4))} W ${/}${if (((Related_Table_Photo_Information.Image | getValue:“direction”)>=202.5) && ((Related_Table_Photo_Information.Image | getValue:“direction”)<=247.4))} NW ${/}${if (((Related_Table_Photo_Information.Image | getValue:“direction”)>=247.5) && ((Image | getValue:“direction”)<=292.4))} N ${/}${if (((Related_Table_Photo_Information.Image | getValue:“direction”)>=292.5) && ((Related_Table_Photo_Information.Image | getValue:“direction”)<=337.4))} NE ${/}${if (((Related_Table_Photo_Information.Image | getValue:“direction”)>=337.5) && ((Related_Table_Photo_Information.Image | getValue:“direction”)<=360.0))} E ${/}
... View more
12-09-2021
09:08 AM
|
0
|
0
|
7716
|
|
POST
|
I was able to resolve this - there were two issues. First, within my data expression to get the Average Private Launches per Day of Week, there were two things wrong. The filter expression in line 4 was incorrect and I needed to update it to say "NOT Name like 'Rental%'" instead of "Not Name = 'Rental%'". The count from line 16 is really the count of total survey scans - I need to drill this down to the number of boats. Since each boat has 2 surveys completed each day (for launch/retrieval), I needed to divide this value by 2 in line 31. var portal = Portal("https://www.arcgis.com");
// Group the features by the BLA
var BLA = Filter(FeatureSetByPortalItem(portal,"###",0,['BLA_Used', 'Survey_Date', 'Name'],false), "NOT Name like 'Rental%'");
// group by boat area and date, return count of launches i.e., boat count
var groupBLA = GroupBy(
BLA,
[
{name: "the_year", expression: "EXTRACT(YEAR FROM Survey_Date)"},
{name: "the_month", expression: "EXTRACT(MONTH FROM Survey_Date)"},
{name: "the_day", expression: "EXTRACT(DAY FROM Survey_Date)"},
{name: "BLA", expression: "BLA_Used"}
],
[
{ name: "survey_count", expression: "BLA_Used", statistic: "COUNT" }
]
);
// empty feature array
var features = [];
// iterate over grouped featureset to populate array
for (var g in groupBLA){
var wday = Weekday(Date(g['the_year'], g['the_month']-1, g['the_day']))
var feat = {
attributes: {
BoatArea: g['BLA'],
wday: wday,
boats: g['survey_count']/2,
wday_label: Decode(wday, 0, 'Sunday', 1, 'Monday', 2, 'Tuesday', 3, 'Wednesday', 4, 'Thursday', 5, 'Friday', 6, 'Saturday', '')
}
}
Push(features, feat)
};
// pass feature array into dict
var outDict = {
fields: [
{ name: "BoatArea", type: "esriFieldTypeString" },
{ name: "wday", type: "esriFieldTypeInteger" },
{ name: "boats", type: "esriFieldTypeInteger" },
{ name: "wday_label", type: "esriFieldTypeString" },
],
geometryType: "",
features: features
};
// convert dict to FeatureSet
return FeatureSet(Text(outDict)) Next, within the data expression to get the Count of Private Launches by Day of Week, I needed to correct the Filter expression in line 5 the same way I did above. I also commented out some redundant lines within the GroupBy statement on line 7. var portal = Portal("https://www.arcgis.com");
// Group the features by the BLA
var BLA = Filter(FeatureSetByPortalItem(portal,"###",0,['BLA_Used', 'Survey_Date', 'Name'],false), "NOT Name like 'Rental%'");
var groupBLA = GroupBy(BLA,
["Survey_Date", "BLA_Used"],
[
//{ name: "BoatLaunchArea", expression: "BLA_Used", statistic: "MIN" },
{ name: "cntBoats", expression: "BLA_Used", statistic: "COUNT" },
//{ name: "date", expression: "Survey_Date", statistic: "MIN" },
]
);
var combinedDict = {
fields: [
{ name: "sdate", type: "esriFieldTypeDate" },
{ name: "dow", type: "esriFieldTypeInteger" },
{ name: "BLA", type: "esriFieldTypeString" },
{ name: "cntSurveyScans", type: "esriFieldTypeDouble" },
],
geometryType: "",
features: [],
};
var i = 0;
for (var m in groupBLA) {
combinedDict.features[i] = {
attributes: {
BLA: m["BLA_Used"],
cntSurveyScans: (m["cntBoats"] / 2),
sdate: DateDiff(m["Survey_Date"], Date(1970, 0, 1), "MM/DD/yyyy"),
dow: Weekday(m["Survey_Date"]),
},
};
i++;
}
return FeatureSet(Text(combinedDict)); This resulted in consistent and verifiable results when comparing data between the data expression and Excel: BLA 1 – Private Launches, Saturday AVG serial chart = 18 AVG Excel = 17.88
... View more
12-08-2021
08:07 AM
|
0
|
0
|
4040
|
|
POST
|
Hi @CraigGillgrass - Is it still planned that Workforce will eventually be "absorbed" by Field Maps and go away as a standalone app? Thanks,
... View more
12-07-2021
10:00 AM
|
0
|
0
|
2170
|
|
POST
|
I resolved this using the original set of questions (first screen capture above) in conjunction with an input mask specified for lines 40 & 44. Within the bind::esri:inputMask column, I specified 99:99. This allows users to just enter numbers, the colon is automatically added and the 'Time Elapsed' calculation works perfectly.
... View more
12-07-2021
09:59 AM
|
0
|
0
|
4247
|
|
POST
|
With the help of a co-worker, I have successfully returned related records using an adapted version of @AaronPulver 's blog (see above for link) for using Power Automate with a feature service/Field Maps. Following Aaron's blog up until the Get Edits Redirect step (housed within the Check Status Until Ready step), we then deviate and use the following workflow to retrieve the related records of the table that the webhook is associated with. Basically the goal is this - a new record is submitted to a related table; within my webhook, I want to also retrieve the parent feature information to use within an email notification.
... View more
12-07-2021
09:55 AM
|
0
|
0
|
1509
|
|
POST
|
With the help of a co-worker, I have successfully returned related records using an adapted version of @Anonymous User 's blog (see above for link) for using Power Automate with a feature service/Field Maps. Following Aaron's blog up until the Get Edits Redirect step (housed within the Check Status Until Ready step), we then deviate and use the following workflow to retrieve the related records of the table that the webhook is associated with. Basically the goal is this - a new record is submitted to a related table; within my webhook, I want to also retrieve the parent feature information to use within an email notification.
... View more
12-07-2021
09:54 AM
|
0
|
0
|
1421
|
|
POST
|
Hi @ZhifangWang - I have a Survey report template which is attempting to print 34 photos from inside a repeat. When we attempt to print the report, we get this error: My end users did some testing on Friday and found that: They were able to print a report with 1 photo They were able to print a report with 11 photos They were NOT able to print a report if it had over 15 photos. They cleared browser caches and tried again, but that did not help. This morning I republished the Survey from Connect v. 3.13.234 and tried to generate the report again, however this also did not work. I also re-uploaded by report template to trigger the syntax checker, however the template did not throw any errors during upload. The report template is structured to include information from both outside and inside the repeat (this survey has nested repeats). No maps are included in the output, just the photos and attribute information for them (which is stored in two places - the same table as the photo and a nested repeat). I also opened a Technical Support request in addition to posting this, however any help would be greatly appreciated. My support case number is #02948651. Thank you,
... View more
12-06-2021
05:44 AM
|
0
|
1
|
3775
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 1 | 3 weeks ago | |
| 1 | 09-06-2022 09:14 AM | |
| 6 | 10-24-2024 12:04 PM | |
| 1 | 04-28-2021 09:14 AM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|