Q: Regarding managing Saved Views created by users. I'm testing Saved Views in a child workspace - when I perform a PUT (via API) to replace the parent workspace definition, it appears to delete all Saved View definitions in the child workspace. Is this expected behavior?

Hi Anant, yes this is the expected behaviour - As this is declarative API and when you use a

PUT

operation it replaces the workspace’s definition. The new definition fully replaces the existing configuration in that workspace.

Is there a way we can update the workspace definition via the API without deleting the Saved View definitions?

Hi Anant, I just wanted to let you now that we have open an internal ticket for our Engineers to review this issue - I will let you know once I have more details on this for you 🙂

Hi @Michael Ullock, just wanted to follow-up and check if the team has had a chance to review this - thanks!

Sorry for the delay in getting back to you. We currently have an internal ticket open with our Engineers regarding this issue - Our Engineers are currently working this issue and I will update you ASAP once we have more details on this. Thanks for your ongoing patience here!

@Michael Ullock thanks for the update! This is a critical open question for us to determine how we can expose the saved views and automations features to our end users.

Hi @Anant Dalela, I am happy to report that this issue has now been fully resolved and the Saved Views will not be deleted when you replace the parent workspace definition(via API). Just let us know if you run into any further issues.

@Michael Ullock thanks for the update, will test this out soon! Can you also confirm that the same fix applies to saved automations as well?

Please let me check this for you ^

Sounds good, thanks for the confirmation!