Workbench - Different jobs ID when importing
We are moving from one on-premise server to another on-premise server and we need to set the same Domo Workbench jobs in the new on-premise server.
We exported the jobs to a local backup file in the old server, then we copy the file to the new server and then we imported the jobs from the file to Domo Workbench. Everything was done with the UI interface of Domo Workbench.
However we noticed that all the jobs in the new server have new IDs and are not set to the current dataset in Domo. This means that we need to manually set the dataset for each job and in some config files we need to change the IDs of every job.
Since we are talking about more than one hundred jobs, do you have any suggestion to copy exactly the same job from the old server?
Best Answer
-
This is the intended functionality with workbench when you import jobs from a JSON definition. It creates a new job definition (I'd disagree that this should be the default behavior and should instead ask if you want a new job created). If you're migrating a server you can do some registry hacking to make it think the new server is the old server and it'll re-download the definitions from Domo so all the jobs and everything is the same. You can read more on how to do this here:
Workbench 5.1: https://domohelp.domo.com/hc/en-us/articles/4407023681559-Simplified-Server-Migration-in-Workbench-5-1
Workbench 5: https://domohelp.domo.com/hc/en-us/articles/360058762534-Simplified-Server-Migration-in-Workbench-5
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0
Answers
-
This is the intended functionality with workbench when you import jobs from a JSON definition. It creates a new job definition (I'd disagree that this should be the default behavior and should instead ask if you want a new job created). If you're migrating a server you can do some registry hacking to make it think the new server is the old server and it'll re-download the definitions from Domo so all the jobs and everything is the same. You can read more on how to do this here:
Workbench 5.1: https://domohelp.domo.com/hc/en-us/articles/4407023681559-Simplified-Server-Migration-in-Workbench-5-1
Workbench 5: https://domohelp.domo.com/hc/en-us/articles/360058762534-Simplified-Server-Migration-in-Workbench-5
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0 -
Thanks @GrantSmith it worked very well!
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 296 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 614 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 729 Beast Mode
- 53 App Studio
- 40 Variables
- 677 Automate
- 173 Apps
- 451 APIs & Domo Developer
- 45 Workflows
- 8 DomoAI
- 34 Predict
- 14 Jupyter Workspaces
- 20 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 121 Manage
- 118 Governance & Security
- Domo Community Gallery
- 32 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive