Some negative impacts of the new feature merged beastmode
Hi all,
Recently there is a newly added Domo feature where the 'Merged from datasource..." beast modes will be created when cards that are using the beast modes are moved to a new DataSet.
But we found that this new feature has an effect on the previous data source as well : domo will rename all the beastmodes merged previously (as "name + merged from xxxx") even if we have already adapted their name before and generated automatically another beastmode with the origin name... I understand that this feature allows the future merged cards to still render without errors, but it does make it more difficult from a governance standpoint for the previous merged cards.
As far as I know, we don't have a way to avoid this behavior, so we have to archive/rename all the beastmodes affected as necessary. But we really wish there will have an option to disable this behavior because il will cause us to waste time in some cases.
Thanks for your help,
Yinchuan
Categories
- All Categories
- 1.2K Product Ideas
- 1.2K Ideas Exchange
- 1.3K Connect
- 1K Connectors
- 269 Workbench
- Cloud Amplifier
- 3 Federated
- 2.5K Transform
- 78 SQL DataFlows
- 524 Datasets
- 1.9K Magic ETL
- 2.9K Visualize
- 2.2K Charting
- 433 Beast Mode
- 22 Variables
- 508 Automate
- 114 Apps
- 386 APIs & Domo Developer
- 8 Workflows
- 26 Predict
- 10 Jupyter Workspaces
- 16 R & Python Tiles
- 331 Distribute
- 76 Domo Everywhere
- 255 Scheduled Reports
- 65 Manage
- 65 Governance & Security
- 1 Product Release Questions
- Community Forums
- 40 Getting Started
- 26 Community Member Introductions
- 67 Community Announcements
- 4.8K Archive