Dataflow Naming best practices
I'm trying to create a company wide dataset naming convention. For sources that are direct connectors it's easy. We'll be doing datasource_project or similar. Dataflows seem to be a lot trickier with multiple sources that could be included in the name. So, does anyone have any best practices that would tackle this issue?
Best Answer
-
The Domo Knowledgebase recommends the following for datasets:
DataSets
Utilize suffix/prefix: PROD, INT, QA, or TEMP
Name DataSets using a common format (ex: BU_System_Dept_Suffix; have ABC_Salesforce_Sales_PROD)
Avoid using / or \ in the DataSet name.
Specifically for Dataflows, I try and follow the same rules and also name my dataflow the same as my output dataset, if I only have 1 output dataset. I have found it much easier to find when I am searchin. If I have multiple output datasets, then I put a _DF at end of my dataflow name.
I also try and make use of the tags feature in the data center. That has been a flexible way to identify what type of data is in that dataset since I can apply multiple tags to it.
Hope this helps.
**Check out my Domo Tips & Tricks Videos
**Make sure to any users posts that helped you.
**Please mark as accepted the ones who solved your issue.2
Answers
-
The Domo Knowledgebase recommends the following for datasets:
DataSets
Utilize suffix/prefix: PROD, INT, QA, or TEMP
Name DataSets using a common format (ex: BU_System_Dept_Suffix; have ABC_Salesforce_Sales_PROD)
Avoid using / or \ in the DataSet name.
Specifically for Dataflows, I try and follow the same rules and also name my dataflow the same as my output dataset, if I only have 1 output dataset. I have found it much easier to find when I am searchin. If I have multiple output datasets, then I put a _DF at end of my dataflow name.
I also try and make use of the tags feature in the data center. That has been a flexible way to identify what type of data is in that dataset since I can apply multiple tags to it.
Hope this helps.
**Check out my Domo Tips & Tricks Videos
**Make sure to any users posts that helped you.
**Please mark as accepted the ones who solved your issue.2
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 292 Workbench
- 4 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 95 SQL DataFlows
- 600 Datasets
- 2.1K Magic ETL
- 3.7K Visualize
- 2.4K Charting
- 685 Beast Mode
- 43 App Studio
- 38 Variables
- 655 Automate
- 170 Apps
- 438 APIs & Domo Developer
- 42 Workflows
- 5 DomoAI
- 32 Predict
- 12 Jupyter Workspaces
- 20 R & Python Tiles
- 384 Distribute
- 110 Domo Everywhere
- 268 Scheduled Reports
- 6 Software Integrations
- 111 Manage
- 108 Governance & Security
- 8 Domo University
- 25 Product Releases
- Community Forums
- 39 Getting Started
- 29 Community Member Introductions
- 98 Community Announcements
- Domo Community Gallery
- 4.8K Archive