Can I send a joined hosted feature view to the bin temporarily so I can make schema changes to the participant items?

[SaraSiskavich]

I need to add fields to a table that participates in a joined hosted feature layer view. Right now the schema of the table is locked from modification because of the view.  Can I just send the view to the Recycle Bin so that I can do my thing? Or is the dependency still there even though the view is in the bin? I need to preserve the joined hosted feature view, specifiically the item id, since external applications (not managed by me) hit the view through REST.  

[Laura]

I believe to modify the schema of the table involved in a joined hosted feature layer view, you will need to delete the view (and not just move it to the Recycle Bin) to remove the dependency. If preserving the Item ID is essential, create a duplicate of the view before deleting it, or prepare to notify external applications about any changes. You will most likely be deleting and redoing your view.

[SaraSiskavich]

Laura,

Yes, preserving the item ID is essential.  Can you please elaborate on your advice about creating a duplicate of the view before deleting it?  Isn't a copy of the view just going to create another dependent view on the parent hosted feature layer?  

[Laura]

Based on something I read it sounds like you can note the ID & URL --> delete your view --> add the fields you want --> and then recreate the join view. I would suggest a duplicate of the view for a backup. If you give the new join the same name then the maps, apps that reference that should still retain configurations. 

Looks like Esri is aware of the frustration this brings so an easier way may be on a future roadmap.