The inability to ADD fields to hosted feature layers on which you have created a dependent view using the JOIN Analysis tool is a big problem. The requirement to delete the hosted view, then re-create it, generates tedious re-building work in all dashboards that the layers are used in. Please provide some kind of workflow to make adding fields in this situation less problematic.
One idea is to create a tool to allow easy re-pointing of dashboard components to a new URL (the new URL of the hosted view that has to be re-created).
Alternatively, some way to "suspend" the hosted view, add fields to the hosted layer, then "refresh" the hosted view from the updated layer would also be great.
Thanks.
Jay
+ 1.
This makes so much sense from a data management perspective. ViewJoins are theoretically best practice for data upcycling.
Allowing ViewJoins to mash hosted features together without merging into a new dataset and consuming 'extra credits' (Melvin's voice from Captain Underpants)
Processes
- have some form of pause functionality on the parent layer(s) or on the entire AGOL acct to suspend Views using the parent layers
- this would unlock the schema allowing changes to be made
- unpause/re-activate the service
- refresh function on the VIEW Join layer to allow schema updates (additional/deleted fields) to flow through effectively.
- either a script or inbuilt GUI function to advise of all the affected end products where the schema has flowed through to.
- where a end product (map, app, ExB, Dashboard) is affected, A review popup window opens warning of the schema update and asks for immediate rectification (ie if the symbology, labels, popups, filters were affected by a deleted field) they could be fixed straight away..
Go on ESRI. I know you can do it!
thanks
mw
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.