A simple versioning in the same way that occurs in workflows, so we can not only test our modifications but also do a quality control and not affect the dashboards that are in production.
In addition to the increased safety and reliability to modify the blocks and testing the other new features of losant.
Hi there, am I right to think this wasn’t implemented? I don’t see any updates on the “Platform Updates” on the blog (albeit I scanned it pretty quickly). I agree with the original poster that this would an excellent feature as it would give us the ability to experiment with our dashboards without affecting customers.
Currently it seems the only workaround would be to have a pseudo-customer that we experiment on and then attempt to make those same changes to live customers once we’re satisfied. Thanks!
We’re trying to figure out the best way to experiment with our dashboard without affecting real users. Our setup uses a global dashboard that displays data for each specific user. The problem is that when we add or remove blocks, those changes apply to everyone.
Currently, we’re using two slugs (one for testing, one for production users). However, both slugs point to the same dashboard, which means any change we make still affects all users.
What’s the recommended or best practice for safely testing dashboard changes without impacting existing users?
Would it make sense to duplicate the dashboards (create a “testing” version) and point the testing slug to those instead?
Sorry but no, not implemented yet and not on our short-term roadmap currently.
What you suggest is generally what I would recommend - your testing environment’s dashboard page points to the testing dashboard, and your production environment page points to the production dashboard.