Service scale dependencies for some services not working correctly

Scott_Shenberger

I have a web app that I created in Experience Builder. The app has three services that have several layers underneath it. All three services and their layers have the same scale dependencies in the map viewer (not classic) and function correctly. The problem is when I get to the Experience Builder app where only one service works correctly. I unfortunately cannot sure the url's as the data is sensitive but I have attached a couple of screenshots. All three services are published out to AGOL from Pro and reference back to the original data source.

Thanks

Scott

working service.JPG

Grey Services.JPG

Danielb3

Hey,

I really like your question and your approach to understanding the application. I don't like writing long texts, so I'll list the key things to check:

• If you're working with sensitive data, I assume you're using ArcGIS Enterprise. If that's the case, the data might not be displaying in the application because it's either too large or putting too much load on the server.

What can you do?

• In the server manager, try reducing the number of displayed records (e.g., to 1,000) or increasing the number of instances. This should help the data display correctly.

• Try creating a new map in ArcGIS Pro, add the layers there, and republish the services.

• It’s also possible that the styles are too complex—it's hard to say without seeing the map.

Within the application itself:

• At the layer view level, you can also limit the number of displayed records.

• In the third tab (which opens when creating views), you can limit the amount of "loaded data"—this might be the key to resolving your issue.

If you're using ArcGIS Online:

• Try splitting the service into several smaller ones. As a test, publish a single layer and check if it works.

• Ensure the coordinate system is Web Mercator.

• If you publish multiple services, you can later create groups in the web map, achieving the same effect. Moreover, this has additional advantages, as you can configure each service separately with a widget. This way, any future changes, such as overwriting the service, won’t break the entire application.

• If you have many layers, there’s always a risk that future changes will impact the data. While fewer services generally improve app performance, whether you have three or eight services shouldn’t be too problematic.

Let me know if any of this helps!

To help me diagnose the issue, show me how things are set up.
Let me know if you're using ArcGIS Online or ArcGIS Enterprise, and how you're publishing the data.

Best Regards,
Daniel