Hi Kevin,
I wonder if you are running into an issue we recently identified? We have seen some "invalid json" errors when there is a Domain defined in the services you are rendering, that do not have any values specified. When there are no coded value domains, we don't handle this case well.
If this is your case, there is a Workaround in the meantime.
First thing
1) Lets identify if this is in fact your issue. Can you inspect the JSON of the services you have in your map
- here is an Example of the JSON endpoint you should be inspecting using one of our sample services (https://sampleserver6.arcgisonline.com/arcgis/rest/services/CommercialDamageAssessment/FeatureServer... )
- Search for some text that looks like this "codedValues": []"
- essentially that text is showing an empty array of Values
- An example of JSON might look like this
{
"name": "MATERIAL",
"type": "esriFieldTypeString",
"alias": "MATERIAL",
"domain": {
"type": "codedValue",
"name": "MATERIAL",
"codedValues": []
},
2) Workaround: If you have found such a case, here are the workaround steps
- Identify which Geodatabase domains have this issue in your source geodatabase.
- Add a minimum of 1 coded value to the domain
- Republish the services.
Is this your case? If not (or even if so), if you can share your webmap with me, I can help identify what's up.
Thanks,
Heather