Anyone using Data Set Views?
Answers
-
Hi @Joe_M
I'm a big fan of DataSet Views. They allow for simple ETL operations (aggregation, filtering, joining - even calculated fields) and load in real time as they don't have to send the data off to be processed so they're typically much quicker. Another nice feature is that you can use them in ETL 2.0 dataflows so if you have a large dataset that you constantly are doing the same filtering on you can create a view with that filtering and use that as your input to reduce the amount of processing time an ETL would take.
Another nice thing I like to utilize them for is to rename columns to a human readable format and utilize that as the input on a card. This way if the underlying dataset needs to change you can just change it on the dataset view itself instead of on all of the cards tied to the original dataset.
In addition to this, my understanding is that they don't count against your row limit in your instance (if you have one).
Hope you enjoy playing around with them. They're one of my favorite features.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
Thanks - this is really helpful!
0 -
One other question - can you lock them to a user? In other words, if User A can only see sales from the Northeast, could I create a DataSet View that only shows sales data from the Northeast and then tie that to User A's login credentials (in other words, a faux PDP)?
0 -
They're just like any other dataset. PDP is the preferred method for restricting access but in theory you could filter the view and then only share it with that user.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
Interesting...
0 -
Just to reiterate I don’t recommend that method of permissions. PDP is the way to go when you need to filter data for specific users. Do PDP based on a specific group or groups and then add specific users to that group (or dynamically)
Filtering and then sharing the dataset opens the possibility it could accidentally be shared with others that shouldn’t have access as Domo currently doesn’t have a Can View sharing option and only Can Share or Can Edit
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
Yeah, the more I thought about it the more it didn't really seem like it would work for what I'm thinking of. Thanks as always for the thoughts.
0 -
FWIW AFAIK the PDP polices are inherited at the Dataset Level (not the DSV). Course that opens interesting questions when a view combines data from multiple datasets or PDP enabled columns ... would recommend testing to see what the behavior is there.
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 295 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 608 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 710 Beast Mode
- 49 App Studio
- 39 Variables
- 667 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 44 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 115 Manage
- 112 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive