ETL+ for Agility

Installation Checklist

• Click here to fill out the DataSelf Analytics Deployment Form.

• Click here for ETL+ pre-installation.

ETL+ Connection to Agility

• If you haven’t installed ETL+ yet: ETL+ Deployment Instructions.

• ETL+ users an ODBC to extract data from Agility database. Please set up that ODBC first.

• Login to ETL+ (help here).

• On the ETL main page, right-click Agility on the left panel → Properties.

  • You might leave the Aliasas is, or customize it.

  • If the ODBC requires credentials, click the Lock icon to unlock it, then enter the Login and Password.

  • Device: Leave it as is by default.

  • On the ODBC 64/32-bit Name section, select the correct ODBC Name from the list.

  • Data Source Connection Timeout: Leave it as is by default.

  • Click Connect.

    

• You’ll get back to the ETL page and see tables under the Agility source on the left panel.

Testing a Table Load

Right-click a table on ETL main page’s center panel → Load Now.

• Failure? It’s likely that the prior step wasn’t properly configured. Go back and review it.

• Click the Log icon (top right) to view data load results. Log page help here.

Schedule the Data Load

• On the ETL main page, click Job (top right icon on the center panel).

• The Job page usually comes pre-configured to your source system(s).

  • Overview this page’s configuration. On the right panel, feel free to uncheck tables and Tableau extracts that don’t apply to your reporting needs.

• Run a Job now (optional): click the Run Job (play icon) on the left panel.

• To schedule the data load (optional):

  • Select a Job → Job Properties (wrench icon) → configure the schedule panel → Save

• Click Close -> Close.

Level 1 Testing

The Level 1 Testing checks if the data extraction process finished successfully and row count per extracted table matches with Agility’s table row counts.

ETL+ must have already loaded your data manually or scheduled.

Steps

• Login to ETL+ (help here).

• On the ETL main page, click the top-right Log icon. Log page help here.

• Scroll down on the log page and double-check that no table load failed, and the row count matches with the Agility tables.

Troubleshooting

• Failed to load tables:

  • Check that the user assigned to DataSelf has reading rights to that particular data set.

  • Click Back from the Log page, on the ETL main page, select the failing table on the center panel, check that its SQL Statement on the right panel has correct information.

• Tables with record count different than in Agility:

  • It might be just that new records have been populated in Agility since the DataSelf data load. Reload the data. Click Back from the Log page, on the ETL main page, select the table with incorrect row cound on the center panel, right-click the table on the center panel again -> Load Now. This might take a while if the table has a large data set.

  • The user assigned to DataSelf might have access to limited data sets, such as only data from one Division. Check the user’s security credentials.