DataSelf ETL+ Release History

2021.10.xxxx *** BETA RELEASE ***

Important: Beta version for testing purposes only! It hasn’t been extensevely tested yet.

Download files:
64 bits: soon
32 bits: soon

Released: soon

New Features - Work in Progress

  1. Data Warehouse Column Formatting: Double-click a data warehouse table to enable column formatting and primary key display mode (a + is enabled by the tables).

  2. Data Warehouse Column Formatting: Click + / - by a table name to expand/collapse its column formatting.

  3. Data Warehouse Column Formatting: icon for regular columns.

  4. Data Warehouse Column Formatting: icon for transformed columns.

  5. Data Warehouse Column Formatting: icon for primary key columns.

  6. Data Warehouse Column Formatting: icon for primary key transformed columns.

  7. Design: New page for column design: configure primary key columns, change column formats, apply column transformations.

  8. Design - Column Transformations: Many sources don’t allow transformations during the extraction, or extraction transformations are limited and/or slow. The data is extracted and loaded into a temporary data warehouse table, and then transformed into to official table. These transformations happen in the data warehouse engine, therefore they are fast, efficient and provide a broad range of MS SQL transformation functions.

  9. Design: Select a data warehouse table → Design to open the Design page.

  10. Design: New page shows PK (primary key), Column Name, Source Data Type, Dw Data Type, Transform SQL Expression.

  11. Design - PK: PK check boxes define a table’s primary key columns. Currently:

    1. PKs are necessary to process Update delta refreshes.

    2. No validation if the PK columns are the correct primary key.

    3. No creation of the physical PKs in the data warehouse.

    4. If physical PKs are needed, please create them directly in SQL after the first ETL+ import.

  12. Design - PK: When importing a new MS SQL or Odata table that has PK in the source, ETL+ will automatically recognize and pre-configure its PK.

  13. Design - PK: Check the PK check boxes to change/define the table’s primary key columns.

  14. Design - PK: ETL+ creates the SQL PK columns set to Not Null.

  15. Design - PK: For text-based sources like OData, varchar(max) columns are automatically changed to varchar(50). We recommend reviewing the varchar size.

  16. Design - PK: ETL+ logs the following when MS SQL can’t create/recalculate a PK: "Primary Key failure. PK requires rows with unique values and no NULLs. Review the PK fields.". This means the selected PK columns are not the table’s correct primary key - review/fix the PK configuration.

  17. Design - PK: When upgrading an ETL+ entity, Primary Index columns automatically become Primary Key columns. Oct version?

  18. Design : To view the source’s Column format, click the Refresh icon on top of Source Data Type. Depending on your source, this can take time (even minutes from OData v4).

  19. Design: To change a Column’s format, use its Dw Data Type dropdown menu, or double-click the dropdown and type in the new format.

  20. Design: Column MS SQL transformations available on Transform MS SQL Expression. Ex.: LEFT(ColumnName,5).

  21. Design: Click the column header for Column Name or Source Data Type to sort the list.

  22. Source Properties: Renamed Dw Schema to Schema. This checkbox sets Alias as the schema for tables imported from this source.

  23. Settings - PK: Ability to create data warehouse physical PKs. Reason: PKs can be taxing for data load and storage (CPU, RAM and disk space), but might dramatically improve query performance.

  24. Settings - PK: New “Create PK” dropdown with options:

    1. Update Only: Default option. Only creates physical data warehouse PKs for tables with Update delta feature.

    2. Always: Creates physical data warehouse PKs for all tables with PKs.

    3. Never: Doesn’t create physical data warehouse PKs.

  25. ETL Page - Load Type: Load Type section is now colapsed.

  26. ETL Page - Load Type: Selecting Replace or Update will expand its settings section.

  27. ETL Page - Load Type: Hovering over the Load Type options shows its function.

  28. ETL Page - Load Type: Replace All has been renamed to Load.

  29. ETL Page - Load Type: Replace with Control has been renamed to Replace.

  30. ETL Page - Load Type: Hover over Load: Full load. Delete & load.

  31. ETL Page - Load Type: Hover over Replace: Delta Load. 1st Load. Ongoing: Replace filtered rows.

  32. ETL Page - Load Type: Hover over Update: Delta Load. 1st Load. Ongoing: Add new, update modified rows.

  33. ETL Page - Load Type: Hover over Append: Full load. 1st load. Ongoing: Append.

  34. ETL Page - Replace: Filter column now is a drop down.

  35. ETL Page - Replace: The filter expression is automatically set to Max(FilterColumn).

  36. ETL Page - Replace: Users can customize the filter SQL pressions. For instance:

    1. Integer constant: 1000

    2. Date constant: ‘02/15/2021’ (use quotes around the MM/DD/YYYY date format)

    3. SQL Expressions. Ex.: getdate()-30

  37. ETL Page - Update: Renamed Primary Index to Primary Key.

  38. ETL Page - Update: Primary Key lists the PK columns (from the Design page).

  39. ETL Page - Update: To edit the PK columns, click the Edit icon by the Primary Key or the Design icon on the table.

  40. ETL Page - Update: Use the dropdown to select the Column with Last Modified Value.

  41. ETL Page - Update: The Update filter is automatically set to Max(LastModifiedValueColumn).

  42. Load Engine - Load: The load happens on a temporary table to allow users to query the official table with minimum interruption. Once the load completes, the temporary table becomes the official one. The temporary table is named Schema.TableName_TEMP.

  43. Load Engine - Load: The transition between temporary to official table happens quickly when there are no transformations performed (delete official, rename temporary to official, create <0_EntityID> when applicable).

  44. Load Engine - Load: The transition between temporary to official table happens quickly when there are transformations performed (delete official, insert into official from temp table applying transformations).

  45. Load Engine: Ability to apply transformations after the load (previously, only available during extraction when the source SQL syntax allowed).

  46. Data Warehouse Tables: All tables now show schema (including dbo). <Schema>.<TableName>.

  47. Data Warehouse Tables: Renaming a table only applies to its name, not the schema (schemas might be changed in Source’s Properties and/or Data Warehouse Settings).

  48. Data Warehouse Source: The data warehouse automatically shows as a data source for additional data preparations and transformations.

  49. Data Warehouse Source: This source provides access to all data warehouse tables and views for single-tenant data warehouses (DataSelf Analytics Pro and Enterprise Editions).

  50. Data Warehouse Source: This source provides access to data warehouse tables and views where <SQL schema> = <EntityID> or <SQL schema> = <dbo> in multi-tenant data warehouses (DataSelf Analytics Advanced Edition).

  51. Data Warehouse - Source: Source’s Properties disabled.

  52. Data Warehouse - Source: Source 'sDelete disabled.

  53. Data Warehouse - Source: Use Settings -> Data Warehouse for configuration.

  54. Data Warehouse - Source: Source credentials are sync’ed up its data warehouse configuration.

  55. Data Warehouse - Center Panel: Tables imported from the data warehouse are automatically renamed to <TableName_DW>. Users can then rename them as needed.

  56. Data Warehouse - Center Panel: Tables imported from the data warehouse keep the same SQL schema as from the original source. Ex.: Abc table imported from ERP source using alias as schema will be stored in <Schema>.<TableName>=<ERP>.<Abc>. Upon re-importing it from the data warehouse, this table will be automatically set to <ERP>.<Abc_DW>.

  57. Data Warehouse - Center Panel: When importing a data warehouse table into itself (usually, a mistake), ETL+ will log: "Warning: Data warehouse source table imported into itself. This is usually a mistake. Fix it by renaming the table.". Oct version?

  58. Sources: Addition to native extraction from cloud Microsoft Dynamics CRM. Alpha version.

  59. Source Properties: Checkbox for 0_UnionID. For this version, this field will be populated with “001”.

  60. ETL Log icon now retrieves live cloud log.

  61. Refresh Batch - WTS: Repeat Task checkbox unchecked by default.

Resolved Issues

  1. aaaa

Known Issues

  1. Importing large XML content into varchar(max) might run into error: server stack limit has been reached.

  2. Deleting all Refresh Batches requires going to ETL main page and back to get a new one created.

  3. Changing the data warehouse of an entity won’t show on the bottom left corner until the entity is closed and re-opened.

  4. Sometimes ETL+ is closing unexpectedly after a data load.

  5. Sometimes ETL+ runs into an “Unhandled exception” error. Close and re-open ETL+.

  6. Locking the ETL+ editing when someone else is editing it doesn’t work in some situations.

  7. ETL+ still tries to send email even when set to Cloud notification, or No Notification.

  8. ETL+ delta extraction from NetSuite ODBC might not work when using dates for filtering.

  9. When opening an entity created in prior ETL+ versions, the data warehouse panel will show the source header blank. To fix this, open the entity in the prior ETL+ version, make any modification and save it. Now open the entity in the latest ETL+ and the source header appears.

  10. Importing tables from the data warehouse works correctly but it might incorrectly log an error message.

2021.09.1301 *** LATEST RELEASE ***

Download file

64 bits: https://dataself.com/etl_plus/DataSelf ETL Plus.exe
32 bits: https://dataself.com/etl_plus/DataSelf ETL Plus 32bits.exe

Released: 09/13/2021

New Features

  1. ETL UI: Added '?' help icon on main pages.

  2. ETL UI: User Guide available at https://dataself.atlassian.net/wiki/spaces/DS/pages/1569980439 .

  3. ETL UI: Many buttons have been replaced by icons.

  4. ETL UI: Hover over icons to view their functions.

  5. ETL UI: Hover over data structures such as data sources and tables to view metadata.

  6. ETL UI: Contextual icons - they are grayed out when they don’t apply to selected objects (ex.: selecting a table on the Source panel disables Delete Data Source).

  7. ETL page: Right clicking on the left two panels pops up the icon functions. The pop ups show the icons and their function names.

  8. ETL page: Clean up of the ETL+ main page (some functions have been moved to other pages).

  9. ETL page: ETL SQL Statement’s title shows the selected TableName (or Source.TableName when multiple sources are mapped).

  10. ETL page: ‘Log File’ icon to open local log file in Notepad.

  11. ETL page: ‘Refresh Schedule’ button changed/renamed to ‘Refresh Batch’ icon.

  12. ETL page: ‘Refresh Batch Now’ function moved to the 'Refresh Batch' page.

  13. Multiple data sources: When opening ETL+, the data source(s) will not list its table names by default. This enables a fast opening of ETL+ since it doesn’t have to wait to list source system table names dynamically. Click a data source and the ‘Refresh’ icon to list its table names - this process can take several seconds if the source system is slow to render its table name list.

  14. Multiple data sources: Imports data from multiple data sources within the same ETL+ entity.

  15. Multiple data sources: Source panel shows all data sources created.

  16. Multiple data sources: Data sources are represented by a cylinder icon, and their table name list can be expanded or collapsed with the +/- icon by the data source icon. Tables are represented by a square window icon.

  17. Multiple data sources: Select a table from a data source and click the ‘Add Table’ icon/function to map it to the ETL process.

  18. Multiple data sources: Click the ‘Add Data Source’ icon/function, select a data source type (CSV, MS Excel, MS SQL Server, OData, ODBC), configure the connection information, click Connect (or Save).

  19. Multiple data sources: Configuration of data sources now includes an editable Alias (DSN Alias).

  20. Multiple data sources: Added ‘Save’ button (saves and closes without trying to connect to source).

  21. Multiple data sources: When creating a new DSN, the Alias is auto populated as following:

    1. MS SQL: Database name.

    2. ODBC: ODBC name.

    3. Excel: File name.

    4. CSV: Windows Folder name.

    5. OData: Last word of the OData URL.

  22. Multiple data sources: Configuration of data sources now includes a ‘Dw Schema’ checkbox. When checked, tables from this data source will be stored in the data warehouse using a SQL schema = DSN Alias. When unchecked, tables will be stored in the default data warehouse SQL schema.

  23. Multiple data sources: In the DSN configuration page, use the ‘Change Data Source’ icon to replace it to another type (ex.: from OData to MS SQL).

  24. Multiple data sources: The DSN pages have a Save button (helpful when doing remote DSN maintenance without access to the DSN).

  25. Multiple data sources: Select a data source and click the ‘Delete Data Source’ icon/function to delete.

  26. Multiple data sources: Select a data source and click the ‘Refresh’ icon/function to reconnect to the data source and list its tables.

  27. Multiple data sources: Select a data source and click the ‘Properties’ icon/function to configure its settings.

  28. Multiple data sources: Mousing over the left panel’s data source icons shows its metadata.

  29. Multiple data sources: Mousing over the left panel’s tables from a data source shows its metadata.

  30. Multiple data sources: The center panel organizes the data warehouse tables by data source alias.

  31. Multiple data sources: The center panel data source alias icon is a square with 3 objects in it. You can expand/collapse the list of data warehouse tables with the +/- icon by this icon.

  32. Multiple data sources: Mousing over the center panel’s data source alias icons shows its metadata.

  33. Multiple data sources: Mousing over the center panel’s tables shows its metadata.

  34. Multiple data sources: When a data source has its table names listed on the left panel, and the user clicks that same table on the center panel, the cursor will select the table on the source system list.

  35. Multiple data sources: Clicking on a center panel’s data source alias icon and the ‘Load Now’ icon will load all of its mapped tables to the data warehouse.

  36. Multiple data sources: Ability to import data from the data warehouse for further data prep.

  37. Multiple data sources: When adding a table from a source, the cursor selects it on the center panel.

  38. Load UI: The load UI page is now integrated in the ETL+ application (not a detached layer).

  39. Load UI: Cancel button stops the load process when the table currently loading ends.

  40. Load UI: Cancel button stops the load process between OData extraction blocks and tables.

  41. Load UI: Shows how many rows have been loaded from the table being extracted now.

  42. Load UI: Shows how many rows per table have been loaded: (X rows <action>).

  43. Load UI: Shows the type of load: the <action> variable in (X rows <action>):

    1. Replace All: loaded

    2. Replace with Control: replaced

    3. Update: updated

    4. Append: appended

  44. Load UI: Refreshing a long list of steps scrolls up showing the latest steps at the bottom of the list.

  45. Load UI: Shows at the bottom of the table list when waiting (sleep mode) versus extracting data.

  46. Load UI: Shows when refreshing each Tableau Extract.

  47. Load UI: New background and font colors provide better contrast.

  48. Load UI: Shows Source.TableName when multiple sources are available, otherwise only TableName.

  49. Cloud Watchdog: Monitors ETL+ scheduled refresh cloud logging and sends email notifications.

  50. Cloud Watchdog: Notifies “Missed execution?” when a scheduled Refresh Batch hasn’t started 120 seconds after the scheduled time.

  51. Cloud Watchdog: Notifies “Taking too long?” when a scheduled Refresh Batch takes longer than (10 mins + 1.5 x Last Refresh Time) to complete. This might be an indication that the refresh will not complete.

  52. Cloud Watchdog: Always notifies when ETL+ “Notification Email” is set to “Cloud - Always Notify”.

  53. Cloud Watchdog: Notifies on error when ETL+ “Notification Email” is set to “Cloud - Notify on Error”.

  54. Settings: Creation of the Settings page and added its icon on ETL+ main page.

  55. Settings: ETL version posted.

  56. Settings: Page provides access to ‘Client Info’, notification about ‘3 secs between error retries', ‘Debug’ drop down, ‘0_EntityID Column’, ‘Data Warehouse’ configuration, ‘About’, 'Notification Email’.

  57. Settings: ‘Refresh Batch Notification Email’ includes dropdown for:

    1. Always Notify: ETL+ always sends notification email.

    2. Notify on Error: ETL+ only sends email on error.

    3. Cloud - Always Notify: Cloud Watchdog always sends notification email.

    4. Cloud - Notify on Error: Cloud Watchdog only sends email on error.

    5. No Notification: No notifications from ETL+ nor Watch Watch Dog.

  58. Settings: “Create Now” button added to “New Data Warehouse” page.

  59. Refresh Batch: Renaming ‘Refresh Schedule’ to ‘Refresh Batch’.

  60. Refresh Batch: Re-layout of the page.

  61. Refresh Batch: Bottom left section shows WTS summary configuration.

  62. Refresh Batch: ‘WTS Settings’ button provides access to WTS settings and Apply button.

  63. Refresh Batch: To run a Batch either click the ‘Refresh Now' icon on a batch name, or select the Batch and click 'Refresh Now’ icon on the panel header.

  64. Refresh Batch: Click the 'Delete' icon on a batch name to delete it.

  65. Refresh Batch: ‘Add’ and ‘Create Shortcut’ became icons on the batch name list.

  66. Refresh Batch: List of Refresh Batch Steps shows twice as much vertical real estate.

  67. Refresh Batch: Clearer description of ‘All Data Warehouse Tables (include new ones)’ checkbox.

  68. Refresh Batch: Click a refresh step and ‘Move Up’ & ‘Move Down’ icons to re-order the refresh steps.

  69. Refresh Batch: New step types for ‘Tableau Extract Refresh', ‘Cloud Script’, 'Command Line’.

  70. Refresh Batch: Click ‘+' icon ('Add Script’), and select a script type to create.

  71. Refresh Batch: Select ‘Tableau Extract Refresh’ to configure an extract to be refreshed. These extracts must be hosted at https://dataselfbi.com and pull data from DataSelf's cloud data warehouses.

  72. Refresh Batch: ‘Tableau Extract Refresh’ script requires the extract name.

  73. Refresh Batch: ‘Tableau Extract Refresh’ default values for other fields:

    1. Project = <EntityID>

    2. Parent Project = NULL

    3. Tableau Site = <EntityID>

  74. Refresh Batch: Select ‘Cloud Script’ to provide its name. Consult DataSelf to discuss your cloud script options (such as running other cloud ETL+ extractions, DataSelf Automatic Distribution, and Python custom applications).

  75. Refresh Batch: Select ‘Command Line’ to provide its name and parameters. This will run the configured command line locally. Example of use cases: running locally Tableau extract refreshes, or on-premises DataSelf Automatic Distribution.

  76. Refresh Batch: Select a script step, and click icons ‘Delete Script’, ‘Configure Script', or 'Run Script’ as needed.

  77. Refresh Batch: Removed ‘Refresh Type' since this can now be done directly in 'Refresh Batch Steps’.

  78. Refresh Batch: Moved ‘Debug’ drop down to Settings page.

  79. Refresh Batch: Removed ‘Enabled’ from batch list (not functional yet).

  80. Refresh Batch: Other UI buttons/icons become disabled when editing scripts.

  81. Refresh Batch: Icons on the Steps panel differentiate objects between tables and scripts.

  82. Refresh Batch: Mousing over icons provide their functions and name and/or metadata.

  83. Refresh Batch: Mousing over a table pops up its metadata (DSN and refresh settings).

  84. Refresh Batch: Removed ‘On Demand Data Refresh’ UI with delay start - no longer needed.

  85. Refresh Batch: Shows ETL+ version on the top right.

  86. Refresh Batch: With multiple data sources, Batch Steps show DataSourceName.TableName.

  87. Refresh Batch: Added ‘Tableau Template Deployment’ icon - available to admin users only.

  88. Refresh Batch: ‘Log File’ icon to open local log file in Notepad.

  89. Engine: Notifies when ETL+ doesn’t find the required .NET installed.

  90. Engine: When an extraction errors out, retry 3 times (3 seconds apart).

  91. Engine: When manually running extractions, connection errors prompt for Retry, Cancel or Skip.

  92. OData Extraction: For OData tables without built-in indexes, ETL+ will only extract data in blocks when indexes have been configured in ETL+. Without indexes, such extractions will be continuous (not in blocks).

  93. OData Extraction: Character fields are loaded into varchar(max) in the data warehouse and are limited to the first 250 characters (next release will give users control of target column format).

  94. OData Extraction: When running an RWC or Update extraction from large datasets, ETL+ logs to Acumatica, loads in sets of up to 100 extraction blocks into a temp table, loads the temp table to the target table, logs off, and then repeats this process for the next set of extraction blocks. This helps Acumatica rendering speed, and provides intermediary starting points in case of issues in the middle of the extraction process.

  95. OData Extraction: When processing delta refreshes, the page size will automatically expand when the delta filter cannot get over the next page of data. The expanded page size only applies to the table being loaded. Message: The delta extraction filter requires an Extraction Pagination expansion from <current> to <new> rows.

  96. OData Extraction: Ability to insert texts that include SQL special characters (such as ' \* *\).

  97. OData Extraction: Debug Log file includes OData URLs executed when Debug is set to Level 2.

  98. Acumatica OData v3 delta refreshes: Acumatica does NOT accept GI formula fields (ex.: =[GLHistoryByPeriod.FinPeriodID]) as filter for RWC and Update.

  99. Acumatica OData v4 delta refreshes: Acumatica requires that filters for RWC and Update must not have NULLs and ETL+ extraction blocks must be bigger than the max number of records for each block of records with the same filter value.

  100. OData v4 Extraction: Changed extraction process for large tables when OData v4 refused to render data.

  101. OData v4 Extraction: When working with RWC or Update and using date filters, ETL+ filtering adapts to the date format of the source Acumatica.

  102. OData v4 Extraction: If a table doesn’t have a native OData index, ETL+ errors out and logs “Extraction time out. Table without native OData index. Please create one via Replace with Control or Update.”

  103. ODBC Extraction: Sage Intacct ODBC support.

  104. ODBC Extraction: Quickbooks Online ODBC support.

  105. OBDC Extraction: MongoDB ODBC support (non-relational database).

  106. OBDC Extraction: Using native MondoDB ' (single quote) or ANSI [] (brackets) around reserved words and nested collections.

  107. ODBC Extraction: Support to views from source system (previously, only tables).

  108. Logging: ETL+ logs description and time for new functions/scripts (Tableau Extract Refresh, etc).

  109. Logging: When launching ETL+ via command line, add the 3rd parameter “1” and ETL+ will log locally “Start ETL+” even before loading the cloud metadata.

  110. Logging: Posts Source.TableName when multiple sources are available, otherwise only TableName.

  111. Logging: Posts the number of rows loaded.

  112. Logging: Posts the type of load: the <action> variable in (X rows <action>):

    1. Replace All: loaded

    2. Replace with Control: replaced

    3. Update: updated

    4. Append: appended

  113. Logging: For large OData tables with RWC or Update, logs when 100 extraction blocks are loaded.

  114. Logging: Posts 32 or 64bit ETL+ version on log refresh headers.

  115. Client Information: ETL version posted.

  116. Client Information: The following fields were moved to more relevant pages: Data source, Settings, 0_EntityID Column, Notification Email.

  117. Client Information: Creation of a Dropdown for DataSelf License type (DataSelf ETL+, VAR, DIY, Advanced, Pro, Enterprise). Only available for super admin.

  118. Client Information: Addition of checkbox to deploy out-of-the-box Tableau Templates for Advanced Analytics.

  119. User Logging Page: ETL version posted.

  120. Error handling: Notifies and logs incorrect Column names used in 'Replace with Control' or 'Update'.

  121. Error Handling: Improved message description when ETL+ can’t connect to its data warehouse.

  122. Error Handling: Added message describing that MS SQL doesn’t accept insert in timestamp columns.

  123. Error Handling: For certain extraction errors, retry the extraction 3 times.

  124. New Deployments: Removed step to load data now (it caused confusion).

  125. New Deployments: ‘Deploy Tableau Script’ runs on dw3 cloud server the following command line: “C:\DataSelf\<SourceSystem>\Deploy.Bat <EntityID> <DwServer> <DwDbName>”

  126. Super admin: ‘Client Info’ and ‘Refresh Batch’ pages allow the deployment of out-of-the-box ‘Tableau Templates’ (site, tdsx, twb) for Advanced Analytics and QA templates for Pro and Enterprise.

  127. Super admin: Entity creation populates EntityID in Refresh Batch Email Notification’s Subject.

  128. Super admin: Entity creation populates user email in Refresh Batch Email Notification’s Email.

Resolved Issues

  1. Counter of Load UI page fixed (it was always counting 1 extra item).

  2. Handling of OData v4 having more than one table with the same name.

  3. Creation of EntityID now requires a unique ID.

  4. Errors out in case of an attempt to create a duplicated data warehouse Schema.TableName.

  5. Tagging of the NextRefreshTime metadata field wasn’t populating correctly.

  6. More than 4 index fields in Update was looping in some OData extractions.

  7. OData XML extraction of non-standard characters fixed.

Known Issues

  1. Importing large XML content into varchar(max) might run into error: server stack limit has been reached.

  2. Deleting all Refresh Batches requires going to ETL main page and back to get a new one created.

  3. Changing the data warehouse of an entity won’t show on the bottom left corner until the entity is closed and re-opened.

  4. Sometimes ETL+ is closing unexpectedly after a data load.

  5. Sometimes ETL+ runs into an “Unhandled exception” error. Close and re-open ETL+.

  6. Locking the ETL+ editing when someone else is editing it doesn’t work in some situations.

  7. ETL+ still tries to send email even when set to Cloud notification, or No Notification.

  8. ETL+ delta extraction from NetSuite ODBC might not work when using dates for filtering.

  9. When opening an entity created in prior ETL+ versions, the data warehouse panel will show the source header blank. To fix this, open the entity in the prior ETL+ version, make any modification and save it. Now open the entity in the latest ETL+ and the source header appears.

  10. Importing tables from the data warehouse works correctly but it might incorrectly log an error message.

2021.03.3103

Release date: 03/31/2021

Download Files

64 bits: https://www.dataself.com/etl_plus/DataSelf ETL Plus 64bits - 2021.03.3103.exe

32 bits: https://www.dataself.com/etl_plus/DataSelf ETL Plus 32bits - 2021.03.3103.exe

New Features

  1. Integrated IP Whitelisting. If ETL+ can’t connect to DataSelf cloud servers, it whitelists the new IP once the user enters the correct product registration information.

  2. Friendlier installation. ETL+ is now an executable-only application. One just needs to download and run it. No installer, no changes to the Windows environment, no need to Run as Admin (unless in some systems when creating Windows Task Schedule tasks).

  3. ETL+ automatically sorts columns alphabetically when adding new source system tables.

  4. Enable SELECT * from MS SQL and OData data sources. Preview only works with MS SQL sources.

  5. OData extraction ignores duplicated column names (avoiding OData → SQL extraction errors).

  6. Refresh Schedule page: “All Tables” checkbox to include new tables added to the ETL process.

  7. Refresh Schedule page: “Tableau Subset” checkbox runs a dedicated Tableau refresh batch for the selected Refresh Schedule. Example: the default Refresh Schedule refreshes all Tableau extracts overnight, and a 2nd one refreshes a subset of Tableau extracts hourly. The creation of Tableau refresh batches continues to be a manual process done by DataSelf.

  8. Refresh Schedule page: “Create Shortcut” checkbox to create ETL+ auto refresh shortcuts.

  9. Refresh Schedule page set to 800x600 resolution.

  10. Refresh Schedule page lists Schedule ID (3rd parameter when running ETL+ via command line).

  11. Windows Task Scheduler: “Repeat tasks every” X minutes (ex.: run every 5 mins starting at 8am).

  12. Windows Task Scheduler: “For a duration of” X hours (ex.: run every 5 mins starting at 8am for 12 hours). To configure indefinite tasks, set duration to 24 hours.

  13. Windows Task Scheduler: Enable configuration of “Recurs every” X days (ex.: once a week).

  14. Windows Task Scheduler: Schedules tasks into the future (to prevent users from mistakenly configuring tasks in the past).

  15. Windows Task Scheduler: UI re-layout for better clarity and more real estate for configurations.

  16. Speed: “Update” delta refresh creates data warehouse indexes for the filter and index columns.

  17. Speed: “Replace with Control” delta refresh creates a data warehouse index for the filter column.

  18. SQL Integrity: “Update” delta refresh turns varchar(max) filter and index columns into char(50).

  19. SQL Integrity: “Replace with Control” delta refresh turns a varchar(max) filter column into char(50).

  20. When running ETL+ for the 1st time, the DataSelf cloud servers connection only happens after the user has accepted the EULA.

  21. If ETL+ can’t download the EULA: it’ll show the EULA page blank (probably an internet connection, firewall or antivirus issue).

  22. When ETL+ can’t connect to DataSelf cloud servers: shows error about IP whitelisting and/or firewall and antivirus adjustments. And then tries to whitelist IP (see feature 1 above).

  23. Super admin: Settings page to select, modify or new data warehouse and its SQL schema. Blank schema = EntityID. Enter the new name to change the schema. Ex.: dbo.

  24. Super admin: Data warehouse configuration page has a Multi-Tenant checkbox. Check it for Advanced Analytics data warehouses, and uncheck it for Enterprise Analytics.

  25. Super admin: Client Info page: “0_EntityID Column” checkbox to create this column.

  26. Super admin: ETL+ logging in the cloud.

  27. Super admin: ETL+ cloud auto refresh log includes EntityID, TableName, Begin Date/Time, End Date/Time, Rows Before, Rows Deleted, Rows Updated, Rows Kept, Rows Inserted, Rows After, Refresh Criteria, Result Type, ETL+ User, Refresh Schedule ID, Refresh Schedule Run ID, Windows Computer Name, Windows Username.

  28. Super admin: “Entity” box converts all characters to lower case.

  29. Super admin: Creation of new OData entities sets the OData extraction blocks to 1000 records and 100ms pause (instead of 0 recs and 0ms pause which causes issues).

  30. Super admin: Wider Entity ID column on the Entities page.

Resolved Issues

  1. Super admin: Issues when creating new entities.

  2. The 32-bit version wasn’t saving ODBC credentials.

Known Issues

  1. When configuring Acumatica OData delta refreshes, in the case that OData doesn’t render the indexes of a table (Acumatica bug?), you might get an “invalid type for an index” error message. To fix it, keep the delta configuration as is, change the “Load Type” to “Replace All”, do a table refresh, and switch back to delta refresh.

  2. Failing to entering correct credentials 5 times in a row closes ETL+ but allows immediate 5 new re-attempts. The correct process is to force a 5 minute wait after 5 failed attempts.

2021.02.2803

Release date: 02/28/2021

Download Files

64 bits: https://www.dataself.com/etl_plus/DataSelf ETL Plus 64bits - 2021.02.2803.exe

32 bits: https://www.dataself.com/etl_plus/DataSelf ETL Plus 32bits - 2021.02.2803.exe

New Features

  1. Move Windows User variables to the Windows ProgramData area.

  2. Simplifies running ETL+ and its auto refresh processes regardless of Windows users.

  3. Collaboration: When a user is editing an ETL+ entity, other users can only log, view or copy its settings. To release editing to other users, Save the entity or close ETL+.

    Other users trying to edit it will receive the message: “username is currently editing this entity. You can only view it. To re-load the modified entity, exit and re-enter ETL.”

  4. Collaboration: When a user tries to edit ETL+ but the metadata has changed by another user, ETL+ gives the message: ETL+ metadata has changed. In order to edit your ETL+, please exit and re-enter to re-load your metadata.

  5. Allowing users to open more than one ETL+ at the same time.

  6. When running Refresh Schedules in parallel, log each of them on their own block (easier to read log file).

  7. Table Load Types in Refresh Schedules: Refresh Schedules can run the default table load type (Refresh All, Replace with Control, Update, Append), or force a "Replace All". This helpful when using delta refreshes on a frequent schedule, and then forcing a replace all on a less frequent schedule to capture old records that have been deleted or modified.

  8. ETL+ lets the same Refresh Schedule run in parallel, but might issue the error message: [DS ERROR : 0902] ETL+ cloud log conflict. Two or more ETL+ are running the same Refresh Schedule at the same time. The data refresh might be ok.

  9. ETL+ allows the refreshing of the same data warehouse table in parallel. Users need to understand the implications of using this feature since it can lead to data consistency issues. Ex.: it’s Ok to append different data sets in parallel, but a full refresh in parallel is likely not desirable.

  10. When editing ETL+, add an * to the Save button to indicate changes haven’t been saved yet. Clicking Save removes the * flag.

  11. Support to OData v4. First release. Test it before using it for production.

  12. Resized ETL+ UI to fit small resolutions down to 800x600.

  13. ETL+ UI can be switched between default size, full screen mode and minimized.

  14. New redesigned ETL+ metadata for better auto documentation, faster performance and reporting.

  15. Upgrade from prior ETL+ versions requires the re-creation of entities, users and statements.

  16. When refreshing tables on ETL+ UI, the refresh progress indicator shows the Refresh Schedule name at the top, the table counter and % progress inside of the circle, and the table being imported at the bottom.

  17. Show ETL version and 32/64bits on the main page.

  18. Ability to define MS SQL Server data warehouse’s database schema. The default schema = ETL+ EntityID. ETL+ admin users can set the schema to any other value (such as dbo). Multi-tenant data warehouses' ID=1 will always have schema = ETL+ EntityID.

  19. RWC and Update will do the first refresh in full refresh mode.

  20. Removed dozens of locally saved variables that are no longer used (they were used before metadata moved to the cloud).

  21. "Leave without saving?" when a user tries to close ETL+ without saving changes.

  22. For users with access to multiple entities, ETL+ remembers the last entity opened.

  23. Show ETL version and 32/64bits on the top right of main pages.

  24. Strong encryption of ProgramData info.

  25. Log changes to the source system’s connection string.

  26. Left and right trim to all user input fields (avoids spaces in usernames and passwords).

  27. ETL+ captures who saved an ETL SQL Statement version. Currently, only available in the ETL+ metadata.

  28. More informative error message when ETL+ cannot connect to its metadata or data warehouse.

  29. If two or more ETL try to refresh the same table at the same time, if the table has RWC or Update, it might give the error message: [DS ERROR : 0910] Two or more ETL+ tried to refresh the XYZ data warehouse table at the same time. This can cause data consistency issues. Please run a full refresh for this table again.

  30. ETL+ version number set to YYYY.MM.DDNN (NN is sequential starting on 01).

  31. ETL+ EULA and About pages inform the latest ETL+ version and URL for download (in case users are installing an older version accidentally).

Resolved Issues

  1. New features number 1 and 2 resolve several auto refresh friction points.

  2. Fixed data auto refresh not running from some servers via command line.

  3. Fixed a testing feature that prevented ETL+ from connecting to the cloud from some servers.

  4. Fixed the auto email of new product registrations.

  5. Fixed ETL+ Excel and CSV data sources to include headers on row 1.

  6. Fixed Update and Replace with Control refresh from ODBC sources.

  7. Fixed error message showing data warehouse structure names.

2021.1.001.1301

Release date: 01/13/2021

Download Files

64 bits: https://www.dataself.com/etl_plus/DataSelf ETL Plus 64bits - 2021.1.001.1301.exe

32 bits: https://www.dataself.com/etl_plus/DataSelf ETL Plus 32bits - 2021.1.001.1301.exe

New Features

  1. Multiple refresh schedules.

  2. Add Debug Mode dropdown to Batch page. Levels: Debug Off, Debug L1, Debug L2. The debug applies to each DSBI site, and all of its refreshes and users.

  3. Allow ETL+ to run multiple refreshes of the same Entity in parallel.

  4. Make UI 99 to be sorted by EntityID (not Entity Name).

  5. Add the dw name to the bottom left corner of the ETL+ UI.

  6. Improve UI titles and descriptions for clarity and self documentation.

Resolved Issues

  1. Test "Communications" and "User" tables with all fields from Sage CRM source.

  2. Scheduler isn't remembering the saved schedule settings.

  3. ETL+ was hanging in WTS. Issue with the feature that puts notifications on the system tray.

  4. When trying to upload 2 tables now, on the dw table list: clicking on a table, pressing and holding Crtl and clicking on a 2nd table crashes the ETL.

  5. Log when refresh runs via shortcut shows [DS ERROR: 9997] - Thread was being aborted.

2020.4.012.1402

Release date: 12/14/2020

Download Files

64 bits: https://www.dataself.com/etl_plus/DataSelf_ETL_Plus_64bits_2020_4_012_1402.exe

32 bits: https://www.dataself.com/etl_plus/DataSelf_ETL_Plus_32bits_2020_4_012_1402.exe

New Features

  1. Create button on the Source Tables column for "Include".

  2. When creating the ETL+ password, re-label "Password" to "New Password".

  3. Selecting DBs in the MS SQL credentials page: Refresh Button to reload the list of DBs.

  4. Delete Data Warehouse Table now has a "Confirm Deletion?" prompt.

  5. Password cannot have # as the only special character. Message: Password cannot have # as the only special character.

  6. For CSV Data Sources: "The first row has a Column names" should be checked and grayed out and non-editable.

  7. For CSV Data Sources: "The first row has a Column names" Delimiter should have comma ',' and grayedout and non-editable.

  8. Replace with Control: Order By field box removed. It automatically creates the index based on the Control field.

  9. Debug Mode creates a log file: Log entityID_debug.txt.

  10. Support for NetSuite ODBC.

  11. Download CSV and Excel files with URLs with strings after the file name.

  12. Ability to use subqueries in SQL Statements.

  13. 0_EntityID to all tables.

  14. Replace with Control delta refresh.

  15. Update delta refresh.

  16. Download CSV and Excel files from URLs into DS_SourceFiles folder where the ETL+ is, and then extract data to data warehouse.

Resolved Issues

  1. Refresh and Upload buttons fail with THROW Error.

  2. The ETL is not accepting edits in Client Information and Refresh Schedule. DS ERROR 04000 - Transaction Failed.

  3. When saving a data warehouse table, ETL shows: "Do you want to cancel all changes made in this section?".

  4. In the Microsoft Excel data source, "the first row has a Column names" should be checked.

  5. It takes too long to enable other functions after saving a SQL Statement.

  6. Fixed OData extract: DSID: nfr_wac_acumatica1, Dw Table: 'TST jn - Prod Order Detail - In Process Released', Upload fails.

  7. It wasn’t running the Tbl refresh at the end of the auto refresh. 

  8. The data refresh email should only be sent when running the full refresh. 

  9. Mapping of Odata fields failed.

  10. When adding New Table, the cursor will allow to change this new table name. However, it can only save the new name if all other table names listed are above "New Target Table".

  11. The ODBC Data Source box had two Connect buttons.

  12. Using Preview in OData on some tables causing closing, freezing or error message.

2020.4.010.2701

Release date: 10/27/2020, First Release

Download Files

64 bits: https://www.dataself.com/etl_plus/DataSelf_ETL_Plus_64bits_2020_4_010_2701.exe

32 bits: https://www.dataself.com/etl_plus/DataSelf_ETL_Plus_32bits_2020_4_010_2701.exe

Released Features

  1. Minimum system requirements: 1 CPU, 2GB of RAM, 5GB of free diskspace, Windows 10, Windows Server 2012 R2 or newer, 32 and 64bit.

  2. Installation process: EULA, user credentials and token, IP whitelisting, connection to data source, scheduling the data auto refresh via Windows Task Scheduler (WTS), refreshing data now, and optionally maintaining ETL+ metadata.

  3. Microsoft certified application.

  4. Creation of Windows Task Scheduler (WTS) task to run the data auto refresh, including schedule and user to run WTS service.

  5. Cloud-based ETL+ metadata allows remote maintenance.

  6. Cloud uptime of 99.9%.

  7. Data source built-in connectors:

    1. ODBC (32 and 64 bits)

    2. MS SQL Server

    3. Odata version 3

    4. Excel (will prompt to install MS Access driver if required)

    5. CSV (will prompt to install MS Access driver if required)

  8. Refresh of tables and subsequent Tableau data sources via encoded batch files.

  9. Auto data refresh email notification.

  10. Data load type: Replace all.

  11. Create evolution bar for the data extraction when running via ETL+ UI.

  12. Add refresh evolution process in system tray when running as a service.

  13. Stores data and metadata in SSL secured multi-tenant AWS MS SQL Server data warehouse.

  14. Upload data to AWS cloud servers via SSL secured IP-to-IP connection.

  15. Locally encrypt user credentials to ETL+ and on-promises systems.

  16. Credentials using user token, and requiring user to create an user with their email and complex password (minimum of 8 characters with lower/upper case, numbers and special characters).

  17. If a users fails to enter correct credentials 5 times in a row, block access for 5 minutes.

  18. ETL+ UI panes: source tables, data warehouse tables, SQL Statements.

  19. About page to show EULA and product release.

  20. Data warehouse table functions: new, duplicate, rename, delete, preview, upload now.

  21. Refresh Now with options to Refresh Full, DW only, Tableau only.

  22. Refresh Now with counter of 9 seconds (configurable), and buttons for Cancel, Pause, Run Now.

  23. ETL SQL Statement with Edit Mode and Confirm button.

  24. Locally saved ETL+ log file with refresh steps.

  25. Email refresh process log to maintenance users.

  26. Creates shortcut on Desktop to run ETL+ auto refresh processes.

Keywords: DataSelf ETL+ Release Notes. DataSelf ETL+ Upgrade. Versions. Latest Versions.