Hello - I have a point layer with contingent values that Field Maps Designer in ArcGIS Enterprise 11.5 thinks has true curves. When I look at the layer in the 'Offline' settings in Designer, it shows that this layer has true curves:
I've never seen this before ever,
How is that possible for a point layer? Needless to say, the layer cannot be edited in Field Maps.
It edits in Map Viewer and it edits in a Sidebar with the Edit widget
Solved! Go to Solution.
Ok so this whole thing turns out to be a false positive. That is to say, the 'true curve' warning has nothing to do with being able / not being able to create this feature in Field Maps.
Instead, this is all about the contingent value class and setting a 'require' on the edit form:
This is for Field Maps only, for the web map edit edit widget or an edit widget in an app it is - once again - much more forgiving:
You can't set a 'require' for the form element for the contingent value attribute that defines your edit template. You then also cannot set a 'require' on the 'dependent' contingent value attribute if <NULL> and <ANY> are allowed as a contingent value pair in your contingent value class. Doing so throws an 'unsupported form element' error in Field Maps.
Once <NULL> and <ANY> are removed from the class, a 'require' can be set on the dependent attribute form element.
This threw me off because Pro complains if you do not have NULL and ANY - but only until you open the attribute pane and add the dependent value.
I consider this now solved and will mark it as so if no one else does.
Ok so this whole thing turns out to be a false positive. That is to say, the 'true curve' warning has nothing to do with being able / not being able to create this feature in Field Maps.
Instead, this is all about the contingent value class and setting a 'require' on the edit form:
This is for Field Maps only, for the web map edit edit widget or an edit widget in an app it is - once again - much more forgiving:
You can't set a 'require' for the form element for the contingent value attribute that defines your edit template. You then also cannot set a 'require' on the 'dependent' contingent value attribute if <NULL> and <ANY> are allowed as a contingent value pair in your contingent value class. Doing so throws an 'unsupported form element' error in Field Maps.
Once <NULL> and <ANY> are removed from the class, a 'require' can be set on the dependent attribute form element.
This threw me off because Pro complains if you do not have NULL and ANY - but only until you open the attribute pane and add the dependent value.
I consider this now solved and will mark it as so if no one else does.