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 toany users posts that helped you.
**Please mark as accepted the ones who solved your issue.2
Categories
- 7.4K All Categories
- 13 Getting Started in the Community
- 151 Beastmode & Analytics
- 1.8K Data Platform & Data Science
- 54 Domo Everywhere
- 2K Charting
- 1K Ideas Exchange
- 905 Connectors
- 239 Workbench
- 343 APIs
- 77 Apps
- 19 Governance & Productivity
- 237 Use Cases & Best Practices
- 50 News
- 473 Onboarding
- 573 日本支部