Workbench - ODBC - Global Replacement Variables - Main use of and how to use them?
I cannot find any example, post, or video that clearly shows what Global Replacement Variables are best used for and how to use them (ideally in the query unless they aren't meant to be used here)? I think a solid definition of what the difference is between a 'Replacement Variable' and a 'Global Replacement Variable' would help quite a bit as well!
Ex: Lets say I want to use a Global Replacement Variable to limit multiple Job's query's where clase to include all data since the beginning of 2019, is that a use case for Global Replacement Variables?
SELECT *
FROM dbo.employee
WHERE startDate >= <Global Replacement Variable with correct syntax that reprensents 2019-01-01>
Best Answers
-
A global replacement variable works just as you've described below. Both the global and non global replacement variables allow you to store the last item in a sorted field in your data set.
The global version allows you to use that stored value in other jobs while the non global version is only accessible in the job it was created in.
Additional information about replacement variables, including how to use them, can be found in the 'Connecting to Data using Workbench 5' KB article linked below. Step 19 gives the details you're looking for.
Tanner
Domo EE
**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"2 -
What I understand to be the main difference is that a global replacement variable can be accessed across workbench jobs, whereas a replacement variable is limited to the workbench job you're working on. It's true that the documentation is somewhat limited in this area.
2
Answers
-
Can anyone answer this question.
1 -
A global replacement variable works just as you've described below. Both the global and non global replacement variables allow you to store the last item in a sorted field in your data set.
The global version allows you to use that stored value in other jobs while the non global version is only accessible in the job it was created in.
Additional information about replacement variables, including how to use them, can be found in the 'Connecting to Data using Workbench 5' KB article linked below. Step 19 gives the details you're looking for.
Tanner
Domo EE
**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"2 -
What I understand to be the main difference is that a global replacement variable can be accessed across workbench jobs, whereas a replacement variable is limited to the workbench job you're working on. It's true that the documentation is somewhat limited in this area.
2
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 753 Beast Mode
- 61 App Studio
- 41 Variables
- 692 Automate
- 177 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive