Best Of

Hi everyone,

I am excited to announce the release of the Datasource Swapper! Whether you are building new datasets because you are moving to a new data provider, transitioning away from materialized datasets in favor of Cloud Amplifier, or dealing with forced changes caused by vendor API deprecations, this tool was created to help save you hours of tedious manual updates to move your existing content to your shiny new datasets.

You can read more about this custom tool and get a step-by-step guide to create and run this in your instance here: https://embed.domo.com/embed/pages/8E1vl

The Datasource Swapper is designed to accelerate large-scale migrations by allowing you to re-map content in bulk. Instead of opening every dataset yourself and updating each piece of content, you can provide a simple mapping dataset to this tool and let it handle the heavy lifting.

Key Functionality & Features:

• Bulk Dataset Swapping: Automatically update the input datasource for Cards, Dataset Views, and Magic ETL Dataflows across your Domo instance.
• Mapping-Driven Automation: Uses DomoStats and a simple "Old ID to New ID" mapping to identify and update all dependent assets for any given dataset in one go.
• Proactive Schema Validation: Before committing changes, the tool checks for missing columns or data type mismatches in the target dataset, allowing you to skip problematic pairs or proceed with full visibility.
• Flexible Deployment: Choose the environment that fits your workflow — deploy it as an integrated Pro-Code App using CodeEngine or utilize the standalone JavaScript-based CLI tool for a local experience.

This tool is perfect for Domo Instance Administrators who are tasked with maintaining instance health during structural data changes. Because it requires the ability to deploy CodeEngine packages, create custom Pro-Code apps, and modify instance-wide content, it is most effective when run by an Administrator or a user with elevated permissions and widespread access to update content.

You can dive into the step-by-step implementation guide and access the code here: https://embed.domo.com/embed/pages/8E1vl

Happy migrating!

Hi, @verytiredgirl - thanks for this feedback! We're looking at how we could enhance column PDP to do the first half of what I think you're asking. Here's how this would work (please let me know if I've misunderstood you).

When you create a Column PDP policy, you would have the ability to make the policy apply conditionally based on the value in some identifier column matching a user attribute. So, in your example, your policy would be effectively (I'll write this out in SQL for clarity): CASE WHEN 'RM Email Address' = userAttribute.userEmail THEN 'value' ELSE NULL END

So, that would allow you to selectively mask per-row, but, it doesn't get you the second part: total sales for region CA. We've received this feedback from some other users, too; However, we're treating it as lower priority based on the limited signal we've received and the relatively greater complexity.

Please do consider adding your feedback in our Ideas Exchange: https://community-forums.domo.com/main/categories/governance-security-ideas

Thanks for pushing the boundaries of Domo!