Best Of
Re: Is there a way to bulk-swap values in Pivot table cards?
In Domo, there isn’t a direct out-of-the-box bulk edit feature to replace a specific value or column used in multiple existing cards across different datasets or views all at once. However, here are some practical approaches you can consider:
1. Use a Data Pipeline or ETL Approach
If possible, modify the underlying datasets or views so that the “Old Revenue” column is replaced or aliased by “New Revenue” at the data preparation layer (for example, in Magic ETL or a SQL transform). With this approach, the cards referencing “Old Revenue” will automatically reflect the updated values without needing to update each card individually, as long as the column name remains the same.
2. Duplicate and Update Datasets with Column Aliasing
You can create a new dataset or view that renames “New Revenue” to “Old Revenue” (matching the column name expected by the cards). Then, you can switch the cards to use the new dataset. This method reduces card-level changes, though it does require managing the new dataset.
3. Card-by-Card Update
If modifying the datasets isn’t feasible (e.g., due to dataset structure or dependencies), you would need to manually update each pivot table card to replace “Old Revenue” with “New Revenue.” To speed up this process, you could group cards by dataset and open multiple cards in different browser tabs for editing.
4. Use the Domo API for Automation (Advanced)
If you have access to development resources, Domo’s REST API allows you to automate card updates programmatically. This would involve:
1. Listing all pivot table cards,
2. Retrieving each card’s configuration,
3. Updating the JSON configuration to replace “Old Revenue” with “New Revenue,” and
4. Pushing the updated configuration back to Domo.
This is the only true bulk update method, but it requires programming knowledge and careful testing.
Summary:
-There is no built-in bulk replace for card fields.
-Updating at the data prep level is the most efficient non-API solution.
-Otherwise, manual edits or API-based automation are needed.
Re: Descriptions in PPT and PDF Outputs
I'm shocked that this is a thing. My customer spent a bunch of time creating cards for her board meeting, including descriptions on each that are needed to understand what's included in the report. Now she has to go either manually update every card or add text to every one in her powerpoint. She is NOT happy.
Re: GPG Encrption in DOMO with SFTP Writeback connector
@Vinodh2110 - I'm working through the exact same scenario. There is nothing built in to accomplish this. I'm using a Jupyter notebook to export the Domo data to a file, encrypt it and upload it via SFTP. Please feel free to DM me. I have written a drop-in python class to do all of this pretty easily that I'd be more than happy to share.

Re: APP Studio proliferation challenge
I think this is the same Idea as here, please upvote and add a comment 🙂
App Studio share a specific page with a person or user not the entire app - Domo Community Forum
Re: Descriptions in PPT and PDF Outputs
This is critical as the descriptions are meant to provide insights to our end users who export this data for their use. We have outside customers that need the data that won't ever be in Domo.
Re: Getting error "domo.OnDataUpdate is not a function"
here's the update I got for CSM and this seems to be working fine for now:
Our CS EE Team worked with our AppDevelopment team who shared with us that the package that is currently being used is slightly out dated and will be updated by EOD on the 26th. With that, we would expect this to work as expected by the 26th. Additionally, they shared with me a temporary work around and confirmed that this will work for your use case for the time being.
In the index.html file, if we update the line to <script src="https://unpkg.com/ryuu.js@4 .7.0"></script> adding the 4.7.0 version on the end, this will point to the newer package and will allow your code to work.
Re: domo.onDataUpdate() Bug
I had a similar issue and this is the suggestion I got from my CSM:
Our CS EE Team worked with our AppDevelopment team who shared with us that the package that is currently being used is slightly out dated and will be updated by EOD on the 26th. With that, we would expect this to work as expected by the 26th. Additionally, they shared with me a temporary work around and confirmed that this will work for your use case for the time being.
In the index.html file, if we update the line to <script src="https://unpkg.com/ryuu.js@4 .7.0"></script> adding the 4.7.0 version on the end, this will point to the newer package and will allow your code to work.
Re: Get Dataset information using ryuu.js lib
Your GET request is pointing at localhost instead of Domo's backend API because of where it is running. You are running your app locally so it points at local development environment. In production, when the app is hosted, it will probably route the API request domo.get() as you expect. Check to see if there is a ryuu CLI to preview locally. Otherwise, you may need to deploy the app to see it properly.