Can you use _Batch_Last_Run_ as the date for a recursive dataflow?

Have a dataset that doesn't have a timestamp that is being imported via connector. Can I use the batch_last_run as the date to create the recursive dataflow?
Best Answer
-
The batch_last_run will be the value when your raw data is imported into the system, the currentdate in an ETL would be populated when the ETL actually runs. Depends on what you're wanting to track with your date.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1
Answers
-
You could use it as your partition key but if you're only wanting a single entry you'll want to convert it to a date first before using it as your partition key.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0 -
Or would it be helpful to create a tile with currentdate and run that through, and then proceed making it recursive?
Or maybe I am asking if that would work similarly?
0 -
The batch_last_run will be the value when your raw data is imported into the system, the currentdate in an ETL would be populated when the ETL actually runs. Depends on what you're wanting to track with your date.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1
Categories
- 10.5K All Categories
- 6 Connect
- 916 Connectors
- 250 Workbench
- 463 Transform
- 1.7K Magic ETL
- 69 SQL DataFlows
- 476 Datasets
- 189 Visualize
- 252 Beast Mode
- 2.1K Charting
- 11 Variables
- 17 Automate
- 354 APIs & Domo Developer
- 89 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 246 Distribute
- 62 Domo Everywhere
- 243 Scheduled Reports
- 21 Manage
- 42 Governance & Security
- 172 Product Ideas
- 1.2K Ideas Exchange
- 11 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive