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.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 738 Beast Mode
- 57 App Studio
- 40 Variables
- 685 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 124 Manage
- 121 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive