Select to view content in your preferred language

Unable to click on point in Map Viewer: error code 400: "Unable to perform query. Please check your parameters."

157
2
11-05-2024 10:43 AM
MaggieS24
New Contributor

Hi everyone. 

I have a hosted feature service that I recently published. It was working all fine until I deleted a field that I no longer needed. After that, when I bring the feature service into a map in AGOL Map Viewer, and click on a point, it spins for a second and then no pop-up comes up. Pop-ups are enabled. Every other data layer in that map works. The layer in question does the same thing of spinning and failing no matter what map it is in.

When I run the web traffic I get this response:

{"error" :
{
"code" : 400,
"message" : "",
"details" : [
"Unable to perform query. Please check your parameters."  ]}}

The layer is also being used in a field map. In the field maps app, the layer works fine, folks are able to create and update points as usual. When I bring the layer into ArcGIS Pro, no problems there. 

Last thing, when I bring that layer into a map in Map Viewer Classic, the pop-up works just fine and there are NO errors in the web traffic. 

This layer and the map its currently in are also being used in an experience builder where they need to click on the points and see the data.

Any ideas? I don't want to have to re-publish but that might also just be the easiest fix? 

 

0 Kudos
2 Replies
ToddW_stl
Esri Contributor

Hi!  In the new Map Viewer, have you tried disabling the pop-up, saving the web map, refresh the page, re-enable pop-up, save web map? 

Otherwise, you could try saving the web map in the Classic Viewer if/when the web map and layer are behaving as expected and see if that helps.

0 Kudos
RobBlash
Frequent Contributor

Are you still having issues? I have nightly scripts that run on some AGOL feature services, and they failed with the same 400 error "Unable to perform query. Please check your parameters."

Whatever the issue was seemed to have fixed itself, because after much wasted time trying to troubleshoot the problem, the scripts suddenly started working again.

0 Kudos