Feature Layer View definition issues

[chris-fox]

Discovered a couple issues with the definition of views. To repro deploy 05ad40176eca46b28b6fc99bc55835c1

1. Variables for viewDefinitionQuery and definitionQuery are not being replaced:
   "viewDefinitionQuery" : "({{02d58f8ad9fa4cc497f95a319af14b0d.fieldInfos.layer0.fields.funded}} = 'Yes') AND ({{02d58f8ad9fa4cc497f95a319af14b0d.fieldInfos.layer0.fields.projtype}} = 'Water Distribution') AND ({{02d58f8ad9fa4cc497f95a319af14b0d.fieldInfos.layer0.fields.projstatus}} = 'Board Authorized') AND ({{02d58f8ad9fa4cc497f95a319af14b0d.fieldInfos.layer0.fields.projphase}} \u003c\u003e 'Complete')",
   "definitionQuery" : "({{02d58f8ad9fa4cc497f95a319af14b0d.fieldInfos.layer0.fields.funded}} = 'Yes') AND ({{02d58f8ad9fa4cc497f95a319af14b0d.fieldInfos.layer0.fields.projtype}} = 'Water Distribution') AND ({{02d58f8ad9fa4cc497f95a319af14b0d.fieldInfos.layer0.fields.projstatus}} = 'Board Authorized') AND ({{02d58f8ad9fa4cc497f95a319af14b0d.fieldInfos.layer0.fields.projphase}} \u003c\u003e 'Complete')"

2. It is possible for a view to have a different domain then the source service. In the example see the projtype field. In these scenarios we need to update the definition of the view to pass the correct domain.

Important, we don't want to do this for every field, we only should do this when the domain is different from the source field. If you update the domain definition for every field, it breaks the connection between the original service domain and the view domain and means if you update the source it won't update on the view.

This is a bug in my current python code because the majority of time the domains will be the same and users will want to update the domain on the source and have it update the view automatically.

[chris-fox]

Verified