Best Of
Re: Workflows - create dataset?
Just keep in mind, CodeEngine runs server side code inside of the Domo infrastructure. If there's not a CodeEngine function for what you want to do, you can literally pop open the network tab while performing the action(s) you want to perform, and see the API calls it makes. You can then point CodeEngine at those same endpoints with parameterized payloads to accomplish exactly what you're after.
What you're wanting to do is 100% possible. Now…whether it's worth the level of effort would depend on how many times you need/want to do this. If it's something that needs to be done with any regularity or any meaningful volume, I'd absolutely automate it. If you just need to do it a few times…probably easiest to just do it manually.
Re: Workflows - create dataset?
@Sean_Tully - it sounds like you now need to:
1 - Create a new dataset
2 - Copy a bunch of cards
3 - Rename the cards?
4 - Switch the cards to this new dataset
All of these things are possible, but will likely require you to make a couple of custom CodeEngine functions (which I can talk you through).
Re: Unable to add new filter in App Studio though being owner
Definitely seems like a bug so you did the right thing by contacting Domo Support.
Re: Drill to final dataset report
@James_Lord you are totally right, that endpoint isn't working for me anymore either (but it was working a few years ago).
It's definitely possible to create a report to show which cards allow final drill to table, but it might be a little more involved.
This endpoint will show whether the card has "allowTableDrill" enabled, but you need to pass an individual card Id to it: https://{instance}.domo.com/api/content/v1/cards/template?urns={cardId}.
Using the JSON no code connector and the DomoStats card report, passing the Card ID column using the Dynamic Paramters, you should be able to create a Domo dataset that shows which cards has drill to table enabled.
ellibot
Re: Activity Log: Action definitions?
Here are the Domo Support Reference :
…and one of the Community Forum Posts for references:
VIEWED
- Definition: A user opened or clicked into a card, page, or app tab.
- Does it include scrolling past? No—scrolling past a card without clicking does not count as a "VIEWED" action.
- Contextual nuance: If your app has multiple tabs, a user must actively click into a tab or card for it to register as "VIEWED".
EXPORTED
- Definition: A user exported data from a card—typically to Excel, CSV, or PDF.
- Does it require viewing first? Surprisingly, no. Users can export directly from a dashboard or app view without formally triggering a "VIEWED" event.
- Why more exports than views? This can happen if users use bulk export features or export from summary views without clicking into individual cards
Re: Could alerts work with Column PDP enabled?
Hi, @Shailaja - thanks for posting in the Ideas Exchange! We know we need to provide Alerts capabilities even on DataSets where PDP Column Masking is active. We plan to begin work on this in the near to medium term.
Re: How can I restrict dataset and card access in Domo to specific users, including selected admins?
To restrict dataset and card access to specific users and selected admins—you could try using Personalized Data Permissions (PDP) combined with a custom role and sharing. PDP would allow you to filter the dataset access by user or group, and the custom role would let you limit admin privileges by removing “Manage Datasets” and “Manage Cards”. The would make sure only specific admins retain full access.
Re: Publish and share dashboards and their underlying dashboards to different groups
Durable Sharing Setup for Domo Publications
- Create two groups:
- All (default group, gets all datasets)
- Small (subscribers, gets dashboards only)
- Publish datasets:
- Create a publication containing only datasets
- Share this publication to All
- Publish dashboards:
- Create a publication containing only dashboards
- Share this publication to Small
- Ensure dashboards reference datasets from the first publication (do not include datasets here)
- Automate or govern new content:
- When new datasets are added, make sure they’re in the dataset publication so they’re shared to All
- When new dashboards are added, make sure they’re in the dashboard publication so they’re shared to Small
- Periodically check:
- Datasets are only shared to All
- Dashboards are only shared to Small
By automate, I mean - use some kind of process to make sure sharing stays correct without doing it manually. Such as Python script using the Domo API, or a Magic ETL approach. I don't do a lot of sharing so I don't know if that's available in the API.
Re: default dataset sharing
we ended up creating 2 accounts for everyone, their SSO account is their viewer account and their direct sign on account is their editor account, no dashboards are shared to editors and ETLs are shared via the ETL and not by sharing dashboards.
we created a workflow to auto leaver them from Domo when/if they do leave our company and this is linked to their SSO account.
Domo confirmed that ETLS are shared via dashboard sharing and there is no way round that. PDP will go some way to halp minimize the risk of over exposure but master datasets contain a lot of information thats PII, so 2 accounts and direct sharing to this account is the only way we can see this working.