mapSettings method in feature reports - what changed?
I have a feature report template, an element of which renders a basic map of the polygon record in question. The report generated just fine as recently as July. The season has calmed down, I'm back to run reports and I get an error message that says mapSettings is no longer supported.
Below is a screenshot of the report template.
Below is the result that it produced just fine in July...
And this is the error that's cropping up now when I try to run the report....
mapSettings is still listed as available in the documentation for the feature reports, and lists it as still being valid for the geoshape field. Below is the format for the geometry field in Survey123 Connect.
So......what gives? Any help would be greatly appreciated, as nothing has changed on our end for how reports were run, and we made a few hundred of these earlier in the summer.
@MatthewCarey Thanks for the link.
Can you elaborate on what fixed your issue? I am finding documentation on field types in this context to be scant.
Mine is configured as such:
The cases I've seen have expressed issues with field type being incorrect (like the link you sent) or the value being null or needing to be null. Having trouble imagining what my bind type should be other than what it is.
Thanks for that. That did the trick, sort of. I was at least able to produce the report.
I'm using 3.12 and still have that as an option...
Interesting though is that it no longer seems to pull from the appropriate map. I specify the item id for the map in question, but it seems to pull from the map embedded in the report window.
The image it pulls now....
And the specified web map, which the reports used to pull from pre-update....
Maybe time to page @ZhifangWang, as they responded in the linked post, and may be familiar with the changes that have undermined things.
All I can do with you on that one is commiserate. I agree it's tough watching for the rug to be swept out from under you all the time. I've gotten into the habit of spending ~1 hour per week at work going through all of the release notes and blogs of all of the software I use at work (Normally my Monday mornings, which is why I'm here right now...)
Anyways, I'm back in the office and here's a copy & paste from my updated templates. The "currentLayer" tag here is the new one I was describing:
${image_location | drawingInfo:"currentLayer"| mapSettings:" b2519fd7a45647a0946f50b0535b6ddd":36000| size:175:250:0:0}
I can't even find the blog post that this was first mentioned in, but I see that it's been added to the help doc for the report template:
https://doc.arcgis.com/en/survey123/browser/analyze-results/featurereporttemplates.htm
-----------------------------------------------------------------------
If your survey doesn't contain a map question or you're creating reports for feature layers without an associated survey, the geometry of a question can still be returned using the ${$shape} placeholder.
By default, a map question will display using a default map symbol, regardless of symbology set in the feature layer. You can use the drawingInfo method to extract and use the drawing information stored in a specific feature layer, including the symbol, label, and transparency used. You can specify this information either from the current layer or from a specific feature layer through a provided URL.
${location | drawingInfo:"currentLayer"}
${location | drawingInfo:"https://.../FeatureServer/0"}
If your survey doesn't contain a map question or you're creating reports for feature layers without an associated survey, the geometry of a record can still be returned using the ${$shape} placeholder.
------------------------------------------------------------------------------
And I can confirm that it works for points and area features. In the web map being called, my point features will display a radar box/arrow icon (that's hosted elsewhere) based on the viewing direction if it's available. If not, a blue circle will be displayed. Started working perfectly as soon as I put that flag in there to use current layer from the web map.
