Larry,
I think we've narrowed down what the underlying renderer is complaining about.
The unique value renderer is based on a Date field, and the value for the the Date field is <null>. Something down the chain does not like this.
So
1) I will definitely continue to follow this up, seems like a bug that we are not handling this case.
I will Chat with some other folks to find out the conditions under which the service would be published this way.
2) Try to get you moving forward and beyond this.
Can you try the following for me? In a test project, can you set the Renderer to something other than that date field (
ESRIGNSS_FIXDATETIME) ? or add a specifc Date value to symbolize on, to that to see if gets you around this issue?
I'm attempting to recreate the service as you have it -
Can you give me some details about how you've published it? email me at hmccracken@esri.com
With details like, whether using Pro or ArcMap, what versions of that etc. (if you can share a Pro package or MXD + data subset that would be great too)
"defaultLabel": "<all other values>", "uniqueValueInfos": [ { "symbol": { "type": "esriSMS", "style": "esriSMSCircle", "color": [ 255, 0, 0, 255 ], "size": 8, "angle": 0, "xoffset": 0, "yoffset": 0, "outline": { "color": [ 0, 0, 0, 255 ], "width": 1 } }, "value": "<Null>", "label": "<Null>", "description": "" } ],Wanted to get you something before the weekend - so wanted to reach out. I'll continue to look into this.
Thanks,
Heather
