On the ETL main page, right-click X3 on the left panel → Properties.
On the Microsoft SQL Server page:
The Alias box will be automatically populated, but you can customize it.
Server name: the MS SQL Server instance name or IP address.
Authentication: select the correct one and its credentials if applicable. Read-only rights are required.
Database name: The name of the SQL database for your X3 database.
Click the Refresh icon on the right to load the list of database names.
Use the dropdown list and select the correct one.
You’ll get back to the ETL page and see tables under the Sage X3 source on the left panel.
Sage X3 Company MS SQL Schemas: ETL+ comes pre-configured to a sample X3 database with [SEED] as its company SQL schema. On the ETL page center panel, select each table under the X3 header and replace [SEED] with your X3’s company Schema on the ETL SQL Statement panel. Ex.: select the ATEXTRA table on the center panel, and replace on the right panel [SEED].[ATEXTRA] with [YourX3CoSchema].[ATEXTRA].
Testing a Table Load
Right-click a table on the ETL page center panel → Load Now.
Failure? It’s likely that the prior step wasn’t properly configured. Go back and review it.
Scroll down on the log page and double-check that no table load failed, and the row count matches with the Sage X3 tables. Following is an example highlighting two tables and their loaded row count.
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 the correct information.
Tables with a record count different than in Sage X3:
It might be just that new records have been populated in Sage X3 since the DataSelf data load. Reload the data. Click Back from the Log page, on the ETL main page, select the table with the incorrect row count 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.