Solved! Go to Solution.
Hi Russ,
I'm having a similar issue but we're using ArcGIS Server 10.2.2. Reading through Randy's replies it seems like removing the default values fixed the issue, but we aren't using default values. Could it be the inheritance issue you describe?
Thanks,
Brandon
I am having this same issue and as Russ suggested to check if they are listed as inherited under the templates in the REST services. I have domains with default value. Is there a solution without removing the defaults?
Thanks
Abdi
Hi there
I am experiencing this issue...but not sure how / where you set this inheritance.
I have a field with Allow Null Values = NO
And a domain set. - YES / NO
I have no subtypes etc.
Could someone shed some light in how to change this
If you are comfortable with using the REST API to edit the json file ...
In the types section of your feature service, each type has a template section. When you change the attribute that controls the symbology, it will use the this template to set default values. Using the example json below, when your feature's symbol attribute is set to "SymbolValue", the template will set Atribute1 to use "SomeValue" and Attribute2 will be inherited because its value is null. If you want Attribute1 to be inherited, replace "SomeValue" (in line 20) with the word null (it will then look similar to line 21). You do not want to change "SymbolValue" (line 19 in the example) as it sets your symbology.
When working with the REST API, you should backup your feature service before making changes. Experiment with a test feature service to become familiar with the REST API. Use jsonlint.com to validate your json. I would also suggest that you only update the types section with the API.
{ "types": [{ "id": "SymbolValue", "name": "SymbolAttribute", "domains": { "Attribute1": { "type": "inherited" }, "Attribute2": { "type": "inherited" } }, "templates": [{ "name": "SymbolAttribute", "description": "", "drawingTool": "esriFeatureEditToolPoint", "prototype": { "attributes": { "Symbol": "SymbolValue", "Attribute1": "SomeValue", "Attribute2": null } } }] }] }
Immediately after the release of Collector Version 10.4.1, I have suddenly started having this problem.
My template attributes are set to null in json so that does not appear to be the issue.
Can anyone help?
Experiencing this with 10.4.1 on Android too - we're rolling back to 10.4 as it breaks our workflows severely. We've logged it with Esri support and are waiting for a resolution.