When I attempt to rename an already-deployed canvas dashboard a different uname (ex. the name in the first line right between “Dashboard” and the opening curly brace), and then deploy that change, the deployment fails. It says “Publish to Production: Failed to deploy” and then “Failed to destroy the record” (screenshot attached). All subsequent deployments for unrelated changes also fail because the change is already in master.
When I revert that change so it’s using the original uname, deployments start working again. I’ve got some questions:
My best guess for what’s happening: uname is how holistics matches the dashboard to the ones in its system with the numeric IDs (ex. the number in the URL), and because it can’t find the old uname in code, it attempts to delete the dashboard and recreate a new one, but fails to delete the original dashboard? For my own understanding, is that accurate?
Is this intentional or a bug? If intentional, what could be preventing this? (For context, I’m an admin, so permissions shouldn’t be an issue.)
Are renames allowed? If yes, would it cause a new numeric ID (the number in the URL)?
Are deletions allowed? I have not tested this but assume we’d run into a similar issue if my guess above is correct.
You’re correct: When you change the uname of an AML object, Holistics deletes the old object and creates a new one with the same definition.
Additionally, Holistics will generate errors if you delete any object that has dependencies. Changing the uname of an object with dependencies also falls under this scenario.
In your case, it’s likely that your dashboard has an existing embed link.
Unfortunately, right now the only way to change your dashboard uname is to delete the embed link first.
That being said, please rest assured. Our team is aware of this limitation, and letting you remap embeds to dashboards is a key focus for us in the upcoming month.
For the moment, could you let me know a few things so I can best support you:
How crucial it is for you to change the dashboard uname right now?
Ok, perfect! Confirming in this case, there is an embed link. This is not crucial at all and definitely something we can work around, but it is extremely helpful knowing exactly how this works, so thank you so much for your prompt and thorough response.
Ah, I’ve got you! Glad the information was helpful.
We are already working to improve the flow of deleting / changing uname for dashboards with downstream dependencies, like this case. I’ll be sure to let you know once there’s an update, Anya.
