Latest Contributions by Brian_McLeer

Thank you @KeyHunter. In widget.tsx, updating line 1346 from const pictometryUrl = `${props.config.pictometryUrl}?x=${lon.toFixed(8)}&y=${lat.toFixed(8)}`; to   const pictometryUrl = `${props.config.pictometryUrl}?x=${lon.toFixed(14)}&y=${lat.toFixed(14)}`; should fix the issue. I made this update and patched the ZIP on this blog post.   ... View more

Thanks @Neal_t_k, that worked for me.   ... View more

Thanks @ewilde , glad its working for you!  ... View more

Hello @ewilde,  would you be able to send any browser console logs when trying to do the PDF output to see if it gives errors or warnings? ... View more

Thank you @StephanieW, just posted on the ArcGIS Online Ideas board.   ... View more

Hello @NairiSevajian, there is nothing missing from the current filtering options that @Neal_t_k provided. I wouldn't call it a use case, but as a user of other tables (say attribute tables in ArcGIS Pro  or Enterprise/AGOL Webmaps), I would expect to be able to sort on any field present in a table as that seems like a standard table behavior. This idea could be expanded to other fields as well in the content table view. A use could would be where you want all of your content in a folder to show, but the filter would hide anything not within your filter. ... View more

Hello @StephanieW, I should clarify the app I am referring is an older Citizen Problem Reporter that was deprecated after the 2/25 AGOL update. When trying to use it, the dialogue box below appears. The old CrowdsourceReporter had category-specific geofencing built in. It could check what boundary a pin was in and then decide which request types were available based on that location. If someone was in the wrong service area for what they were trying to report, it would block the submission and show them who to contact instead. The new Reporter Instant App added a boundary restriction option in the June 2025 AGOL update, but it only does a simple in/out check against one polygon layer. It can block submissions from outside the service area entirely, but it can't tie specific request categories to specific boundaries. There's no way to say "you're in a service area, just not the right one for this type of request." So right now you can block people from submitting outside the overall service area, and you can show warnings with contact info for the wrong boundary using Arcade expressions in the form, but you can't hard-block category-specific submissions the way the old app did. That would require Esri to add that functionality in a future release. Also the image above ties to BUG-000183047: "Some ArcGIS Solution items using retired ArcGIS Configurable Apps are prompting 'Retired Item Type'"   ... View more

2/26/26: No updates to widget, but recent February 26 update to AGOL OOTB EB Draw widget added import/export JSON files. These JSON files are compatible to be imported into this widget. This widget does not currently support an export from this widget into the OOTB EB Draw Widget.  ... View more

2/26/2026: Add custom measurement units via settings to appear in linear and area unit drop downs. Thank you @ncramer11 for idea and beta testing Add import/export XML in settings to transfer/backup settings configurations Updated settings UI to match more to Jimu standards ... View more

It looks like out of the box no, but you could maybe create a new field that is concatenated to be the order you want, then use a POI role in the Create Locator GP tool. From there, use the Place Name field for your concatenated field. You can still define City, State, Zone, etc. fields in the field mapping for the POI locator role type.  ... View more

Thank you @ncramer11 . I could look at adding custom units in settings that can be set up by developer and an option to add it to linear and area drop down lists if configured via settings.  ... View more