Skip to main content

​
Intro

Workbench is a Windows-based application that lets you upload DataSets to Domo, which includes the following:
  • You can upload data from databases via data queries in ODBC/OLAP System DSNs, CSV and delimited text files, Microsoft Excel spreadsheets, Jira, QuickBooks, JSON and XML namespaces.
  • You can upload data manually or through scheduled jobs.
  • Workbench validates data and securely transfers data to Domo.
This article answers some frequently asked questions about Workbench. Select a question to expand and view the answer.

​
Workbench System Questions

Workbench is available in all of the same languages the Domo product is available in. As of May 2019, these include the following:
  • English
  • Japanese
  • French
  • German
  • Spanish
  • Chinese
Workbench syncs automatically with the user language set on your machine. If your desired language is not available, the default language will be English.If you would like Workbench in a language not shown in the list above, please contact Domo Support.
Yes, both 32- and 64-bit Windows versions are supported.
Yes. Workbench concurrently supports both 32- and 64-bit ODBC drivers.
Due to OAuth 2.0, each user is allowed 50 refresh tokens per client. This means that only 50 Workbench machines can be running at a time per user. If you set up more machines using the same set of credentials, you will likely run into problems while executing jobs.
Port 443 bi-directional

​
Security Questions

All data transferred from Workbench into Domo’s production systems is sent using encrypted HTTPS sessions, the same technology you typically use to conduct online banking and online purchases. Additionally, all sensitive data is encrypted using AES (Advanced Encryption Standard) and the key is stored in Workbench, not in Domo, so only Workbench can decrypt the values.
Workbench stores access credentials for ODBC DataSets. To properly protect these credentials, Workbench uses industry standard AES-256 bit encryption or RSA encryption with a key stored locally on your computer (depending on the length of data being encrypted). Workbench enforces encryption automatically so users do not have the opportunity of mistakenly storing their passwords or other credentials inappropriately.
When you first connect to Domo via Workbench, Workbench leverages your Windows system proxy settings. You can open your proxy settings for editing by clicking and selecting Proxy.
Domo Support can provide you with an IP to whitelist. Note that although unlikely, the IP can change at any moment and without notice, resulting in Workbench job failures. It is advised that you whitelist by DNS name if possible. (e.g. instance.domo.com).
Workbench is configured by the client from an access control perspective. Workbench allows users to upload DataSets into Domo to enable KPI card creation and automated updates. Users select DataSets (System DSNs, flat files, Microsoft Excel spreadsheets, JIRA, QuickBooks, JSON, XML namespaces) to which they already have access. Workbench can connect to DataSets only if the Microsoft Windows system running the software can reach the DataSet, and if the machine has access to read the DataSet files or databases.
No, Workbench does not modify your original data. It is designed to read and transmit data to Domo. Workbench does let you modify the data going into Domo through transforms, calculations, and joins.Note: For database connections only, if your ODBC driver supports read/write, any queries you pass into your database can be considered a “write.” For example, temp tables, inserts, or deletes are entirely possible with Workbench and database connections. Consider using read-only credentials for your database connections if there is cause for concern.
No.
Workbench uses a temp directory (%PROGRAMDATA%\Domo\Workbench\DomoCache) to stage incoming data. If you have many DataSet Jobs with a large number of rows, this temp directory can fill up with a large amount of data. Make sure the C:\ drive has a reasonable amount of free space for these files. These files are cleared when the job is complete and are not permanently stored.
Workbench 5 uses OAuth to authenticate so access tokens are no longer needed, and Workbench OAuth doesn’t expire. However, it can be invalidated. When a user changes their password, it invalidates any existing OAuth tokens.
Yes. Changing your password causes your OAuth tokens to expire, and Workbench is no longer authenticated.

​
Questions About Workbench 5 Tasks

Workbench has no row limit for a single upload job. You can use a `lastvalue` variable to upload rows incrementally. For more information about query parameters, see Understanding the Workbench 5 User Interface.
Yes, Workbench can be executed directly from a command line and/or added as a task in an ETL package.For more information about running Workbench from the command line, see Running Workbench from the command line.
When using a MySQL driver, you can decrease its memory usage and improve its performance by configuring parameters for the DSN.Follow these steps to configure your MySQL DSN:
  1. Open the the Windows ODBC Data Source Administrator by entering “ODBC” in the Start Menu search, then selecting “Data Sources (ODBC)”.
  2. Select your DSN, then click Configure.
  3. Click Details to display additional settings.
    1. In the Connection tab, mark the Allow big result sets box.
      When selected, the driver does not set packet limits for results.
    2. In the Cursors/Results tab, mark the Don’t cache results of forward-only cursors box and the Force use of forward-only cursors box.
      When selected, the driver does not cache results and uses forward-only cursors.
Note: Workbench does not need anything other than “forward only” cursors and the MySQL ODBC driver performs better using the “forward only” cursors option.
When running a job on a schedule, if the file is not located on the local machine Workbench is running on, you must set up impersonation for access rights.Follow these steps to set up impersonation:
  1. Click the icon in the left-hand icon bar.
  2. Double-click the name of the job you want to set up impersonation for.
  3. Select Configure.
  4. Click Impersonation to expand that section.
  5. Check the Requires Impersonation box.
  6. Enter your domain, username, and password in the boxes.
  7. Click Validate.
If you are connecting to a file on a domain file share that the Workbench computer is not on, the domain impersonation will not work if you are not on the domain computer. You will have to give domain access to it.Follow these steps to give domain access:
  1. Click the icon in the left-hand icon bar.
  2. Double-click the name of the job you want to provide domain access for.
  3. Click Edit under “Source.”
  4. Enter the network file path in the File Path field.
  5. Check the File on an external network box.
  6. Enter your credentials.
  7. Click Apply.
Say you have a dataset set up to update every hour, and you keep getting an error when you’re trying to run the job in Workbench. More specifically, you’re not able to add that job to the queue because it is either already queued or currently executing.There are a few reasons why this error can occur and ways to avoid it:
  • The current job could be in a non-responsive state. If a job is running longer than expected, open a case with Domo Support to investigate the issue further (support@domo.com).
  • You can also restart the Workbench service, which will flush the queue. Normal workflow of Workbench jobs should return after restarting. If restarting the service does not return your Workbench to normal operation, please open a case with Domo Support (support@domo.com).
You can create a new job that will append the data that has changes in the RDBMS (Relational database management system) since the last load. Follow the steps below to do it.
  1. Perform the initial load of the data using Create New Data Source.
  2. The two key setup lines in the SQL that are very important are as follows:
  • Where “ReportDate” > '!{lastvalue:ReportDate}!'
    Ensure the Where clause contains the field that holds the value that indicate the changes since last load. The '!{lastvalue:ReportDate}!' contains the last value for the Query Variable as shown (see the Query Variable Setup section below). Call the Query Variable the same name as the field in the query that indicates the changes since the last Load.
  • Order by
    Ensure you have an Order By clause in the SQL statement, since it will be the value from the last row that will be saved in the Lastvalue variable. If you don’t order by the column that contains the change data capture field, then you might not get the changed rows in the query.
  1. After the initial load change, the job will start appending data to the existing dataset, as shown in the example below:
Can I save Workbench jobs to a shared folder? I want multiple users to be able to access and edit the jobs, but I can’t figure out where jobs are saved on the drive.All Workbench jobs are saved in the cloud and tied to a specific login, not saved locally. Therefore, the recommended solution to this problem is to install Workbench on a common server then create an admin user to be used by all users who need to modify jobs. Thus, all these users will be able to access the jobs, and you will not need to worry about saving copies of the job on a physical drive. Although multiple users can use Workbench simultaneously, only the first opened instance will get the live updates from the Workbench service. We generally do not recommend having multiple instances of Workbench open because of multiple people have the same job open and are making changes, the last person to save will overwrite all other changes.
Both groups will run at the same time.
The current version of Workbench doesn’t allow you to separate the operating system from the application data, but you can work around this issue using hard-coded symbolic links. The following example shows how a user moved his DomoCache directory to the E: drive:mklink /J "C:\ProgramData\Domo\Workbench\DomoCache" "E:\Domo\Workbench\DomoCache"What does it mean when Workbench says “Live updates are not available”?This could mean a few different things. If another person is running Workbench on the same computer, this message will appear. This could also appear if there are port conflicts with other applications on the computer. To fix this, go to Workbench Settings, and in the Notifications section you will be able to update the Port.
Yes. Workbench 5 allows the mass import/export of job files. Click and select Export. You can then choose a save folder and select all of the jobs you want to export.
Yes, if you need this ability, please reach out to your account team for evaluation.
Not by default, but Workbench does have this as a configurable option.
The query builder is in the Source pane. This may give you a list of tables, views, and procedures. Be aware this is not compatible with all database types.
The data is stored in %PROGRAMDATA\Domo\Workbench\DomoCache. Currently you cannot move the staging folder.
Jobs are tied to the Workbench installation in which they were created. If you wanted to share a job, you would need to export that job on the Workbench installation in which it was created then import it into the second installation of Workbench.
Note: It is not recommended to have the same job running on two different instances of Workbench at the same time. If you do export a job from one and import it into another, be sure to remove it from its original Workbench instance after successfully importing it into another.

​
Troubleshooting

Ensure your Windows username is not the same as the PC name. Windows 10 appears to enforce this. Older versions of Windows may also be impacted.
You can find the logs in the following directory: C:\Users\NAME_OF_USER\AppData\Local\TempThe file names are Domo_Workbench_<datestamp>.log and Domo_Workbench_<Datestamp>_001_DomoWorkbench64.log
You must be logged into Windows with an active session for QuickBooks integrated applications to run unattended.
The “Unsafe Save” dialog is displayed when your local job configuration and the remote job configuration stored in Domo do not match up or the job is currently running. To prevent the loss of data, you must first wait for the job to finish if it’s running, then re-sync your local configuration with Domo. This can be done by either clicking Revert or pressing F5 on your keyboard to refresh your entire job list. Unfortunately you will lose any changes that you have made when you take either of these actions. If your job runs long enough or frequently enough that you constantly see this dialog when attempting to make changes, you likely need to temporarily turn off the Workbench service, make your changes, then re-enable the service to start running your newly modified job.