Is there a way to add unique id or constant to workbench
I am seeking to aggrigate a historic set of data. The problem is the data pull date, a critical peice of identification, is stored in the title of the report - and does not exist in any of the fields. There is no way to identify WHEN in time the data in a row exsisted, or if it differs from the next time that identical row appears in another report.
Example
Row ID | Categorical Variable | Categorical Date | Report Identifier |
123 | Blue | 1/1/2018 | 3/1/2018 |
456 | Red | 2/1/2018 | 3/1/2018 |
789 | Green | 3/1/2018 | 3/1/2018 |
123 | Blue | 1/1/2018 | 4/1/2018 |
456 | Red | 2/1/2018 | 4/1/2018 |
987 | Black | 3/1/2018 | 4/1/2018 |
123 | Blue | 1/1/2018 | 5/1/2018 |
987 | Black | 3/1/2018 | 5/1/2018 |
654 | Red | 4/1/2018 | 5/1/2018 |
I have tried to add a concatenated statement of the max date on a report but it returns the max date of each row... I would prefer not to load each report manually and blend/etl it since it's a standard report that should be workbenched. Is there a way to pull in data from an excel sheet's meta info or title? or a way to attach a unique constant per run? A date would be ideal but i will settle for anything i can use to compare unique id to unique id transactionally.
Best Answer
-
Yes, historically existing rows will need a different solution. Perhaps you could start with the dates you wanted in the spreadsheet, then you could remove that date column and then insert the transform in the workbench job, and see if they append to each other.
Aaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1
Answers
-
In your workbench job, you can add a "Transform", a new column of a calculated field.
This will insert a new column called 'Test Date', and if you set the workbench job to append, each new set of rows will have a new value in that 'Test Date' column.
Aaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 -
Thanks, that will absolutely help for data imports in the future - but appending historic data it will all look like "today" when in actuality it is different variables (past dates) that apply to each dataset exclusively.
0 -
Yes, historically existing rows will need a different solution. Perhaps you could start with the dates you wanted in the spreadsheet, then you could remove that date column and then insert the transform in the workbench job, and see if they append to each other.
Aaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1 -
This might be the only (work-around) solution with the current way Workbench runs.
I actually did end up doing just this and it works.
Thank you!
1
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
- 58 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