Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Click here for instructions to upgrade your ETL+.

2023.10.1905.

...

44 *** CURRENT VERSION ***

Expand
titleDownload, Release Notes, Release Date

Latest Release Download Links:

New Features v2023.10.1905

  1. Source metadata refresh via the Agent (Source Objects panel):
    Source metadata refresh via the Agent: New feature that can work with the local Agent or from remote servers.

  2. Command line for Source metadata refresh via the Agent: New -rd <source PK> command line executes the source refresh defined by the PK.

  3. Source metadata refresh via the Agent: New Refresh via Agent buttonicon (circular arrow with the letter A) to start the source metadata refresh via an Agent.

  4. Source metadata refresh via the Agent: As a starting point, the Agent to run the source metadata refresh is the last one that successfully loaded a table from this source.

  5. Source metadata refresh via the Agent: Users can change the Agent to run a source’s metadata refresh by using a new Source properties' icon on the top right.

  6. Source metadata refresh via the Agent: When changing the Agent to run a source’s metadata refresh, uses can select any assigned Agent to their entity, plus the local computer’s Agent, or via the UI.

  7. Source metadata refresh via the Agent: On the page above, the user can define whether the agent change to run the source metadata refresh will be on this ETL+ session only or permanently.

  8. Source metadata refresh via the Agent: The assigned Agent to refresh a source’s metadata can be found on the popup when hovering over a source.

  9. Source metadata refresh via the Agent: When selecting a source, its metadata’s Refresh icon will show if it’ll run via the UI or an Agent.

  10. Source metadata refresh via the Agent: When right-clicking on a source, its metadata’s Refresh icon will show if it’ll run via the UI or with an Agent.

  11. Source metadata refresh via the Agent: When right-clicking on a source, its metadata’s Refresh icon description shows if it’ll run via the UI or the Agent name.

  12. Source metadata refresh via the Agent: The new icon shows the Agent name that will run this task.

  13. Source metadata refresh via the Agent: The new icon shows None if no Agent is allocated to this source (no Agent has ever successfully loaded a table from this source).

  14. Source metadata refresh via the Agent: When starting this process in an ETL session, the source’s icon changes to a Source Refresh icon.

  15. Source metadata refresh via the Agent: This task works with sources and zData Warehouse.

  16. Source metadata refresh via the Agent: When the metadata has been refreshed in the cloud, the user receives a prompt notifying it. Clicking Ok on the prompt and the source icon returns to normal reloading the metadata into the ETL session.

  17. Source metadata refresh via the Agent: Triggering metadata refreshes are logged as User Actions.

  18. Source metadata loading from SQL is significantly faster.

  19. Upgrade install via the Agent: When clicking to upgrade installations via the Agent on the Entity page, it prompts for Yes/No.

  20. Upgrade install via the Agent: It upgrades all the entity’s installs that have active Agents.

  21. Upgrade install via the Agent: For Agents running, the upgrade takes less than a minute.

  22. Upgrade install via the Agent: For Agents not running, the upgrade takes place when the Agent runs.

  23. Upgrade install via the Agent: The upgrade happens behind the scenes, it won’t interfere with running ETL+ sessions such as running Jobs or open ETL+.

  24. IT Debug mode ON: New debug mode using the command line interface (-d).

  25. IT Debug mode ON: Logs the beginning of a Job run with the local .NET version.

  26. IT Debug mode ON: Logs locally many OS, hardware, and internet access variables in a new log file.

  27. IT Debug mode ON: Desc and SourcError log 5,000 characters (up from 500).

  28. IT Debug mode ON: This debug mode also runs when Setting → Debug is set to Level 2.

  29. IT Debug mode ON: When running a Job with this setting ON, the beginning of the table load takes a few extra seconds to start because of the logging of system environment variables locally.

  30. Online metadata: ETL+ shows on the bottom a message when it’s unable to connect to its metadata.

  31. Online metadata: When the metadata is disconnected, the user can continue to use ETL+ as long and it doesn’t need to exchange data with the metadata.

  32. Online metadata: When the metadata is disconnected, the user receives a notification when it tries to exchange data with the metadata.

  33. Online metadata: Once ETL+ re-connects to the metadata, it operates normally again.

  34. User Interface (UI):
    UI: refined ETL page Action icons: cleaner and green for load actions; all others are black.

  35. UI: refined Job page Action icons: cleaner and green for load actions; all others are black.

  36. UI: refined Source page Action icons: cleaner and black.

  37. UI: refined Log page Action icons: cleaner and black.

  38. UI: Agent actions have 'A' on their icons (e.g.: Run Job via Agent).

  39. UI: Minor corrections and misspellings.

  40. UI: Source “Add Table” action relabeled to “Add Table to Target”.

  41. UI: Hovering over an ETL Source now also shows its PK.

  42. UI: When “Add Table to Target”, if the table already exists, the message now says: <TableName> already exists. Add it as <TableName>(n)?” E.g.: Abc already exists. Add it as Abc(n)?”

  43. UI: Job Steps now show the same table icons as the ETL page, thus making it easy to view Load types (All, Replace, Upsert, Append, Freeze).

  44. UI: Target icons for Expand and Collapse columns are now always available.

  45. UI: Expand columns shortcut: Alt + Shift + Right Arrow.

  46. UI: Collapse columns shortcut: Alt + Shift + Left Arrow.

  47. UI: Remapped Help icons pointing to the new KB pages.

  48. UI: Added page titles to Running Job, Table Loading, and Source Metadata Refresh.

  49. UI: Job Refresh Email header rearranged for easier email preview reading.

  50. UI: Windows Task Bar: The Job UI shows a new taskbar label: “ETL+ Job <JobID> <EntityID>”.

  51. UI: Windows Task Bar: The Log UI shows a new taskbar label: “ETL+ Log <EntityID>”.

  52. UI: When an entity is open, an easier-to-understand notification when another user saves it.

  53. Job Load UI: Now shows the JobID as a title.

  54. Job Load UI: Now with a black background.

  55. Job Load UI: Now shows the ETL+ version.

  56. Log UI: Now opens shifted to the right and bottom from the screen center (to avoid opening behind the main ETL page).

  57. UI: Run Job and End Job icons: Always active regardless of Job status.

  58. UI: Moved End Job icon under the Run Job menu.

  59. UI: Product registration email now has updated links to KB.

  60. UI: Entity page: Shows the EntityPK.

  61. UI: Entity page: Seach now works across all columns.

  62. UI: When prompting to upgrade/downgrade an entity with this version, clicking No goes back to the Entity page (no more prompt with link to the KB).

  63. When running Jobs and a source’s captured metadata is NULL, ETL+ will no longer load the source metadata. This is an unnecessary step.

  64. ETL+ downloads and installs Microsoft Access Database Engine 2016 Redistributable, when necessary.

  65. When a source doesn’t have proper credentials, Jobs will skip its table loads.

  66. Customized metadata: Standardized database name.

  67. OData extraction: Tables with no Design’s Key+ configured will extract without pagination.

  68. Cloud logging: Some Log Descriptions could have a huge amount of characters. Descriptions are now truncated at 500 characters.

  69. Cloud logging: Some SourceError descriptions could have a huge amount of characters. Descriptions are now truncated at 500 characters.

  70. .NET SQL commits/rollbacks apply to the ETL+ metadata.

  71. Security: Security upgrades to DataSelf’s website (including new security tokens for file downloads). More secure ETL+ process to download files from DataSelf’s website. More secure ETL+ process to extract Excel files from SSL-based websites. More secure ETL+ process to extract Google Sheets from SSL-based websites. More secure ETL+ process to extract CSV files from SSL-based websites. More secure ETL+ process to extract OData from SSL-based websites. Stronger encryption of private data saved on the local HD. Stronger encryption of private data saved in the metadata. Stronger encryption of ETL+ private data. Stronger encryption of Agent private data. Stronger encryption of IP app private data. Stronger and more limited ETL+ metadata credentials. Embedded DataSelf’s Google Sheets JSON string in ETL+. Encrypted DataSelf’s Google Sheets JSON string. Creation of hidden folders following revised Microsoft best practices. New location and file name for ProgramData ETL+ configuration file. New location and file name for a user’s ETL+ configuration file. New working folders named “DataSelf Corp”. New ETL+ user passwords won’t work in versions older than 2023.07. Admin email alert about SQL injection attempt. ETL downloadable exe files' pubic key updated in the metadata.


Fixed Issues v2023.10.1905

  1. Replace delta configuration for table joins only accepts MAX(FilterColumn).

  2. Running Jobs from sources that don’t have their source metadata captured can hang the Job refresh indefinitely.

  3. Sometimes, the source metadata was deleted. For instance, opening an entity with a prior version and then with this one deletes the captured source metadata.

  4. The first attempt to open ETL+ by a regular user usually fails (ETL+ just dies). It works normally after that. Fixed.

  5. Upon upgrading an entity, connections to SQL might be set to Windows Authentication.

  6. If adding a zDw SQL View to ETL+, it won’t recognize that the object name already exists in SQL and will allow saving it.

  7. After adding a zDw SQL View to ETL+, trying to delete the ETL+ table will freeze the UI.

  8. Trying to switch a data source from one type to another crashes ETL+.

  9. When running Jobs, if ETL had a data warehouse connection error, it would switch into a failed load for all remaining job steps.

  10. When running Jobs, a single failure to connect to the data warehouse errors out. The process wasn’t retrying 3 times.

  11. In single-tenant data warehouses where sources are set to customized schemas, 0_UnionID columns might not bring in the correct value.

  12. User actions to run a Job via de UI or Agent weren’t being logged.

  13. Odata v3 extraction from GIs with spaces in their names might fail.

  14. Regular users could open pre-saved 99 user UI in DataSelf domains.

  15. Google Sheets: Issues extracting tables with space or line breaks in column names.

  16. Google Sheets: Issues extracting some tables. You might need to re-load the sheet source metadata and remap it.

  17. Importing a table that was already pre-mapped was duplicating the pre-mapped SQL Statement instead of adding the table from scratch again.

  18. Adding new tables sometimes wouldn’t automatically create their Extract SQL Statment.

  19. Excel mappings would not list all columns in the target metadata.

  20. Excel extraction accepts commas in column names.

  21. Excel mapping of files with special characters would fail.

  22. CSV mappings would not list all columns in the target metadata.

  23. Upon logging in, ETL+ does not remember the last open entity.

  24. Email refresh report: Send on Error Only wasn’t working.

  25. SELECTs in Design’s T-SQL weren’t working.

  26. Log page shortcut Ctrl + G on the Job page wasn’t working.

  27. Renaming Jobs #2 or higher wasn’t working.

  28. The Add Job action wouldn’t work after deleting all Jobs.

  29. Forgot Pw button on the login page was emailing the password from prior ETL+ versions.

  30. Source icons on the menu were stretched and blurred.

  31. Target Object icons on the right-click and Action were stretched and blurred.

  32. Extraction of Excel with commas in column names errored out.

  33. If the Extract SQL Statement had ‘0_UnionID’ as part of a column name, 0_UnionID new field was not being created.

  34. Extraction of UNPIVOT from zData Warehouse was crashing the ETL+.

  35. Reimport SQL Statements with constants with no value were converted to NULL. This could cause errors. Conversion removed.

  36. Sometimes, adding an Excel table was putting double single quotes on the SQL Statement, which caused failed extractions.

  37. OData DAC table names were always handled as case-sensitive based on what was in the captured source metadata. This could cause extraction errors. Now it’s only case-sensitive if Acumatica’s SQL database is set to case-sensitive.

  38. Workaround for OData error: “Odata[0100] - The contents of table Note are not available for this user. The remote server returned an error: (400) Bad Request.“ → this is an intermittent Acumatica limitation when rendering large tables via OData without proper indexing in the OData request. Fix: Configure the ETL+ Design’s Key+ index to match with the source's table’s PK (columns list and order), plus configure a delta refresh for this table.

Hotfix v2023.10.1905.28 (fixed issues)

  1. Design page: varbinary(x) data types are failing to save.

  2. Design page: Changes to column data types are only executed during Load All.

  3. Design page: User actions are not being logged.

  4. MySQL Source: Unable to extract tables with data types: geometry and blob.

  5. MySQL Source: Incorrect conversion of data types: tinyint, mediumint, datetime, year.

  6. OData Source: Extractions are not retrying on the initial table load errors.

  7. OData Source: Extractions are not retrying during table load errors.

  8. IP whitelisting: In some installs, ETL+ cannot get out of the IP whitelisting process.

  9. Regular users with multiple entities might be unable to open some entities.

  10. Mapping a new source table already mapped is duplicating the existing target table (instead of adding a new one).

  11. Customizing the ETL+ metadata on a new install from scratch might not save the hidden file with the custom settings, and the ETL+ metadata will default to dw3.

  12. Resetting the password of admin users doesn’t prompt for creating a new one.

  13. Admin users without any entity assignment aren’t able to log in.

  14. Improved error message when a delta refresh filter column has a data type different than expected or is nonexistent.

  15. If a source table has been mapped and customized, adding it again duplicates the target object (duplicates the first target table customizations instead of creating a new fresh mapped table).

  16. If a source table has been mapped and customized, and then is deleted, adding the source table duplicates the previous target object customizations (instead of creating a new fresh mapped table).

  17. Added <ETL username> to several user action log descriptions.

  18. The mechanism that finds table name duplication is case-sensitive - which can cause table name conflicts in non-case-sensitive SQL DBs.

  19. When running a Job and there’s a failure to connect to the data warehouse, the ETL+ cannot reconnect to the data warehouse for the remainder of the Job run.

  20. If a user cannot log in to ETL+ with the error message “This user doesn’t have access to any entity”, 1) be sure the user is added to an entity; 2) if that doesn’t fix it, delete the hidden ProgramData DataSelf folders.

  21. In certain conditions, Upsert & Replace only worked correctly after the first delta load in a given ETL+ session.

  22. Force Replace when Upsert uses the filter value from the Upsert configuration (instead of Replace).

  23. If a duplicated table is renamed, ETL+ won’t allow it to duplicate again.

  24. The load all of OData tables with no indexes might fail.

  25. Unable to auto-creation of ObjectTID column in zLog_ETL and zLog_TableStats data warehouse tables.

  26. The insertion of log lines into the data warehouse zLog tables was partial and logged errors.

  27. Remote upgrades are not working.

  28. OData extractions were not logging connection error retrials.

  29. Relabeled ETL Metadata page: title “Metadata Server” and “Default (dw3)”.

Hotfix v2023.10.1905.35 *** CURRENT VERSION *** (fixed issues)

  1. T-SQL Statements with CROSS JOIN crash when running via Jobs.

  2. Extraction of OData with tables with over 100 pages is not using the Temp2 flow.

  3. OData extraction of large tables with Upsert might switch the Upsert filter to Replace when hitting 100 extracted pages.

  4. OData table extraction with no Design’s Key+ configured is still paginating.

Hotfix v2023.10.1905.42 (fixed issues)

  • DataSelf ETL+ 64-bit: DataSelf ETL Plus.exe (16MB)

  • Released: 03/08/2023

  • IMPORTANT: Only install this version when needing one or more of the fixes below:

  1. Loading NetSuite source metadata sometimes fails. Fixed.

  2. ETL+ can’t connect to its metadata on some computers. It then incorrectly starts the IP whitelisting process. Fixed.

  3. ETL+ can’t list some tables from some Google Sheets. Fixed.

  4. In some installs, sometimes running Jobs stall and never finish. Fixed.

Hotfix v2023.10.1905.44 *** CURRENT VERSION *** (fixed issues)

  1. For some entities, sometimes, Jobs get stuck or just skip all steps. Fixed.

Known Issues

  1. Creating new sources and clicking Connect often doesn’t load the list of tables. Workaround: run Refresh after creating the source.

  2. Sometimes, adding an Excel new source (or CSV), adding a table, and clicking Save will crash ETL+.

  3. New sources with Excel from cloud URLs will only load after closing and re-opening the entity.

  4. Replace is not working in GoogleSheet tables.

  5. ETL page: Confirming SQL Statement changes can take a long time to complete.

  6. ETL page: Saving the ETL page with many source objects can take a long time to complete.

  7. Changing the source’s database of a remote install won’t stick.

  8. Excel mapping: Mapping table names with special characters might fail.

  9. Excel mapping: Mapping column names with special characters might fail.

  10. Settings - Job Notification Email: The dropdown for when to notify might not remember the selection unless the Email box is configured (issued identified with the No Notification option).

  11. It doesn’t notify that it can’t accept SQL passwords with ; (semicolons) using SQL Authentication.

  12. Running a Job via the Agent: if ETL+ can’t connect to the data warehouse, it will end the session without an error and it doesn’t log informing what the issue is.

  13. Job Script: Clicking Properties of a Job Script will set the Job as modified (* on the Save button) even if the Job Script was not saved.

  14. ETL+ might be unable to connect to a customized ETL metadata server. Workaround: run ETL+ via the command line with -md parameter, delete all files from C:\ProgramData\DataSelf Corp\DataSelf ETL Plus, enter the new ETL metadata server connection information → Save.

  15. Replace with a character filter >= '' or ' ' will append rows instead of replace.

  16. OData delta extraction cannot use GUID columns for delta filtering (Acumatica limitation?). When loading a table that has this field used in a delta filter, the ETL+ might retry the table load indefinitely.

  17. Paginated OData extraction (indexed extraction): During a load of a large number of rows, there’s a risk of data duplication for rows inserted during the extraction with an index value lower than the ongoing extraction values. Workaround: Create an index with a guaranteed ascending value for the load (e.g.: CreatedDate & PK Columns).

  18. OData Upsert: The engine includes the Upsert’s LastModifiedValue column as the first index column in the URL. In rare cases, this might cause row duplication.

  19. User 99: ETL+ might not retain OData source metadata from some Acumatica installs. Workaround: Close the entity, then ETL+, then re-open the entity.

...

Expand
titleDownload, Release Notes, Release Date

Download Links:

Released: 7/21/2023

New Features

  1. Extraction Performance: ETL processes run dramatically faster when extracting from MS SQL sources that are hosted in the same SQL instance as the data warehouse.

  2. This improvement also applies to zDataWarehouse re-imports.

  3. ETL+ Configurable Metadata: Now the ETL+ metadata location is configurable. This allows the deployment of the complete ETL+ engine (server, client, and agent) behind a client’s firewall, as well as having an ETL+ solution for testing purposes (with no effect on the production stack).

  4. ETL+ Metadata: Ability to configure the location of the metadata database for a given ETL+ installation.

  5. ETL+ Metadata: Run ETL+ in a command line with -md parameter to configure a custom metadata location.

  6. ETL+ Metadata: When configuring a custom metadata location, click the Default button to set the metadata back to its default location (dw3), and close the dialog.

  7. Saving a Copy of Source Metadata: Now a copy of sources' metadata is saved in ETL+. This copy might contain a list of tables, columns, column formatting, and primary keys if available. This allows users to map new tables and columns more quickly and without the need to be connected to the source database.

  8. Source Metadata: On the Source page, clicking Connect retrieves and stores the source database’s table and column metadata.

  9. Source Metadata: On the Source panel, clicking Refresh retrieves and stores the source database’s table and column metadata.

  10. Source Metadata: During ETL+ loads, ETL+ uses the stored source metadata to build and execute extraction queries. In prior ETL+ versions, ETL+ first read the column list and formatting, built the extraction query, and then executed it. This new approach reduces the time to extract tables, from a fraction of a second to several seconds per table depending on the speed of the source database.

  11. Source Metadata: Since ETL+ can now store the source database’s metadata, users will be able to add tables and columns to their ETL processes without the need to connect live to source systems to read what’s available.

  12. Source Metadata: On this release, ETL+ only uses the in-memory source metadata when adding tables as new objects. If the user edits the Extract SQL Statement, ETL+ will use other methods to resolve column formatting.

  13. Source Metadata: Hovering the mouse over a Source on the Source Objects panel shows when its metadata was loaded to the cloud.

  14. Source Metadata: Hovering the mouse over a Source on the Target Objects panel shows when its metadata was loaded to the cloud.

  15. Source Metadata: When loading a table, ETL+ will load the source metadata to the cloud if that hasn’t been done before.

  16. Saving Mapped Tables' Column Metadata: Now each mapped table has its source and target column metadata saved in ETL+. Users can quickly see that data on the redesigned Design page, this is helpful for maintenance and troubleshooting. Also, this saved metadata allows ETL+ to execute table loads more quickly (in prior versions, it had to read the source and target column formatting before executing a load).

  17. Design page: Redesigned page from scratch.

  18. Design page: The page and its column sizes can be manually adjusted.

  19. Design page: Source PK column(s) added.

  20. Design page: Source PK column(s) (when available) are now numbered based on the source’s PK definition.

  21. Design page: Source Data Type added. It shows the data type received from the source database.

  22. Design page: VarChar column with checkboxes added. This allows users to force the extraction of a source column into a varchar(max) data type in the temp table in MS SQL. This is helpful when MS SQL might have issues accepting the values from a given source data type. Example: a date column with invalid amounts in SQL. Or a source numeric column with dirty data (like strings in some rows).

  23. Design page: DW PK renamed to Key+.

  24. Design page: Key+ tooltip provides clearer information about this column.

  25. Design page: Key+ is now numbered to set the sequence of multi-column unique keys and PK.

  26. Design page: By default, when available, the Key+ comes preconfigured to match the source table’s PK from MS SQL Server.

  27. Design page: By default, when available, the Key+ comes preconfigured to match the source table’s PK from Oracle.

  28. Design page: By default, when available, the Key+ comes preconfigured to match the source table’s PK from OData.

  29. Design page: Logged-in username added at the bottom-left corner.

  30. Design page: Entity ID in session added at the bottom-left corner.

  31. Design page: When changing the Dw Data Type, there’s a revised message to notify users about setting a new T-SQL expression: “Changed data type from <source type> to <target type>. Overwrite T-SQL to: <new T-SQL expression>. Confirm? Recommended: Yes)”.

  32. Design page: When converting a char data type to date, ETL creates TRY_CONVERT. This converts invalid date values into NULL.

  33. Design page: When converting a char data type to datetime, ETL creates TRY_CONVERT. This converts invalid datetime values into NULL.

  34. Design page: Clicking Confirm no longer requires clicking Confirm on the ETL page.

  35. Removed Target Objects → … → Load All Columns. This feature became obsolete.

  36. Remote Upgrade: Now admin users can trigger the upgrade of ETL+ and its Agent remotely (without the need to be logged into the computer with ETL+). This requires an active Agent on the target computer.

  37. Remote Upgrade: Ability to upgrade ETL+ and Agent remotely in Agent-active installations.

  38. Remote Upgrade: The Agent has a new function to upgrade its ETL+ install.

  39. Remote Upgrade: ETL+ has a new command line function to upgrade its Agent.

  40. User Authentication: SQL Source passwords now have new actions: View/Hide Password, Lock/Unlock Password.

  41. SQL Passwords: On an unlocked SQL password, users can view and hide the password.

  42. SQL Passwords: Users can click the Lock Password icon to permanently lock it. Locked passwords cannot be viewed.

  43. SQL Passwords: Unlocking a password will require password re-entry. From that point on, users can view and hide the password.

  44. Data Warehouse SQL Authentication: Support to Azure Active Directory - Password.

  45. Source MS SQL Authentication: Support to Azure Active Directory - Password.

  46. Saved ETL+ user credentials are now encrypted and stored in C:\Users\<username>\AppData\Local\DataSelf_Corporation\ds_lg_info.ds

  47. OData Refinements: Now ETL+ can map and extract PX_ tables and columns that before weren’t directly available via the ETL+ mapping wizard.

  48. OData v4 Refinements: Redesign a part of the processing of OData v4 metadata.

  49. OData v4 Refinements: Ability to read a broader range of OData v4 tables and columns.

  50. OData v4 Refinements: Prior ETL+ versions couldn’t list some regular tables on the Source Panel. This is now fixed.

  51. OData v4 Refinements: Prior ETL+ versions couldn’t automatically list many available columns from some tables during the table mapping. This is now fixed.

  52. OData v4 Refinements: Ability to list and read PX_ tables.

  53. The mapping of OData v3 and 4 tables mimics the source’s column formatting.

  54. The extraction of OData v3 and 4 tables no longer truncates string fields to 255 characters.

  55. Extraction of large OData tables now uses the data stored on the TableName_Temp2 to reset the OData filter to extract the next block of 100 pages. This addresses an Acumatica issue when rendering data from large tables via OData.

  56. For OData with delta extractions based on date filters, the JSON/XML time zone is now ignored. This eliminates the need to read the time zone before the extraction starts (removed Currency table extraction that was previously used to read the default time zone of an Acumatica tenant).

  57. When adding new OData sources, the default page size is 5,000 rows (up from 1,000).

  58. Extraction Engine: The code has been refactored into classes for cleaner execution and maintenance.

  59. The mapping of tables from non-structured sources (like Excel, CSV, and ODBC) mimics the source’s column formatting.

  60. The extraction of tables from non-structured sources (like Excel, CSV, and ODBC) no longer truncates string fields to 255 characters.

  61. ODBC Source Page: Added credentials section.

  62. ODBC Source Page: Made it clearer that the list of available DSNs is 32 or 64 bits.

  63. Now users can open and edit ODBC Sources even on computers that don’t have any DSN.

  64. Replace Delta Refresh: Dedicated metadata filter column (no longer shared with Upsert).

  65. Replace Delta Refresh: Updated the feature description “1st: Insert rows based on the condition. Ongoing: Replace rows based on the condition”.

  66. Replace Delta Refresh: changed labels from “Field” to “Source Field”, and blank to “Target Value or Constant”.

  67. Upsert Delta Refresh: Dedicated metadata filter column (no longer shared with Replace).

  68. Upsert Delta Refresh: Renamed Primary Keyto Unique Key.

  69. Refinements/adjustments to extract Salesforce.com data via ODBC.

  70. Refinements/adjustments to extract Snowflake databases via ODBC.

  71. Refinements/adjustments to extract NetSuite data via ODBC.

  72. Refinements/adjustments to extract Oracle data via ODBC.

  73. Refinements/adjustments to extract Oracle data via native driver.

  74. Google Sheets sources will automatically download the DataSelf JSON Google Sheets file if not available locally.

  75. Now you can add other expressions outside of CTEs (ex.: a table union).

  76. Extract SQL Statement Parsing: Initial Parsing release.

  77. SQL Parsing: Tries to capture the target table’s column list and data types and stores them in the metadata.

  78. SQL Parsing: A new toggle icon on the SQL Statement sets if parsing is on or off.

  79. Parsing ON: Clicking Confirm on a changed SQL Statement will try to execute parsing.

  80. Parsing OFF: Clicking Confirm on a changed SQL Statement will just save the statement to the metadata - no parsing.

  81. Parsing ON: Clicking Confirm on the Design page will try to execute parsing.

  82. Parsing OFF: Clicking Confirm on the Design page will just save the Design changes.

  83. Freeze Table: Added a checkbox to the More Actions target object menu to freeze a table’s content.
    For more see ETL+ Freeze

  84. Freeze Table Loads: Frozen tables can’t be changed via ETL+, unless the table is unfrozen. For more see ETL+ Freeze

  85. Frozen tables retain their delta refresh configurations (if needed again).

  86. Log will show “Skip table” for frozen tables that are part of refresh Jobs.

  87. Hovering over a frozen table shows Load Type = Frozen.

  88. Job Refinements: Fixing some scheduling bugs as well as incorporating weekly and monthly scheduling.

  89. Job Scheduling: Next date/time to run a Job uses a more refined algorithm.

  90. Job Scheduling: Next date/time to run a Job can use scheduling based on weekly parameters (configurable via ETL+ Web - beta release).

  91. Job Scheduling: Next date/time to run a Job can use scheduling based on monthly parameters (configurable via ETL+ Web - beta release).

  92. Job App: Simplified process to select an Agent app. Select it from the dropdown, and click Save.

  93. Job Load Type: Changed to a dropdown list with a new option: Force Replace when Upsert, default for others.

  94. UI Improvements: Source types now have their own icons on the ETL page.

  95. Source Icon: Google Sheets dedicated icon.

  96. Source Icon: MySQL dedicated icon.

  97. Source Icon: MS Access dedicated icon.

  98. Source Icon: MS Excel dedicated icon.

  99. Source Icon: MS SQL Server dedicated icon.

  100. Source Icon: OData dedicated icon.

  101. Source Icon: ODBC dedicated icon.

  102. Source Icon: Oracle dedicated icon.

  103. Source Icon: PostgreSQL dedicated icon.

  104. Source Icon: CSV dedicated icon.

  105. ETL Page: Source types now have their own icons on the Target Object panel (smaller than source icons).

  106. Target Object Source Grouping Icon: Google Sheets dedicated icon.

  107. Target Object Source Grouping Icon: MySQL dedicated icon.

  108. Target Object Source Grouping Icon: MS Access dedicated icon.

  109. Target Object Source Grouping Icon: MS Excel dedicated icon.

  110. Target Object Source Grouping Icon: MS SQL Server dedicated icon.

  111. Target Object Source Grouping Icon: OData dedicated icon.

  112. Target Object Source Grouping Icon: ODBC dedicated icon.

  113. Target Object Source Grouping Icon: Oracle dedicated icon.

  114. Target Object Source Grouping Icon: PostgreSQL dedicated icon.

  115. Target Object Source Grouping Icon: CSV dedicated icon.

  116. Source Properties Page: Source types now have their own icons.

  117. The bottom left corner of ETL+ pages now shows the EntityKey value and metadata URL.

  118. The Job page now shows the data warehouse information.

  119. The data warehouse information under the ETL page title now has a tooltip with more details.

  120. The data warehouse information under the Job page title now has a tooltip with more details.

  121. ODBC Data Sources page: layout re-organized for clarity.

  122. ETL Source panel was renamed to Source Objects.

  123. ETL Objects panel was renamed to Target Objects.

  124. ETL SQL Statement panel was renamed to Extract SQL Statement.

  125. Target Object icons: Dedicated icon to represent tables with Replace.

  126. Target Object icons: Dedicated icon to represent tables with Upsert.

  127. Target Object icons: Dedicated icon to represent tables with Append.

  128. Target Object icons: Dedicated icon to represent tables with Freeze.

  129. Settings page: Layout reorganized.

  130. When clicking actions, the mouse cursor goes to “waiting mode” until the action completes (ex.: on Save buttons).

  131. Source Objects - New Source menu: Removed (Beta) tag from Google Sheets, MySQL, Oracle, and PostgreSQL.

  132. When an entity is open, by default, all objects on the Target Objects are collapsed.

  133. Client Information’s Cloud Script checkbox moved to a better position.

  134. When importing a table from the zData Warehouse, by default, the table is renamed (to be sure it’s not overwritten in case the table hasn’t been mapped as a target object in ETL+).

  135. It’s now possible open/edit existing ODBC sources even when there are no local DSNs.

  136. Target Object icons: A small red dot notifies modified tables that haven’t been saved to the metadata.

  137. User Action Logging and Debugging: Now many ETL+ user actions are logged. This should help collaboration and troubleshooting.

  138. Logging: Many user actions are now logged on the zETL_Log table.

  139. Logging: New logging type = 100 for user actions.

  140. Logging: Saved data warehouse configuration.

  141. Logging: Saved a table’s Extract SQL Statement panel.

  142. Logging: Saved Job page.

  143. Logging: Settings page saved.

  144. Logging: Client Info page saved.

  145. Logging: Table added.

  146. Logging: Table deleted.

  147. Logging: Table renamed.

  148. Logging: Job added.

  149. Logging: Job deleted.

  150. Logging: Job script added.

  151. Logging: Job script deleted.

  152. Logging: Source added,

  153. Logging: Source deleted.

  154. Logging: Agent on a machine added.

  155. Logging: Job App selected.

  156. Logging: Entity duplicated.

  157. Command Line -d (debug mode): Runs ETL+ in local debug mode on the local hard drive.

  158. Command Line -d: There’s a new local file Log_Debug.txt showing information about the environment where ETL+ is running.

  159. Command Line -d: Information logged: OS version.

  160. Command Line -d: Information logged: OS local language.

  161. Command Line -d: Information logged: .NET version.

  162. Command Line -d: Information logged: 32/64-bit platform.

  163. Command Line -d: Information logged: Test the https access to dataself.com.

  164. Command Line -d: Information logged: Outbound port testing.

  165. Command Line -d: Information logged: Available local hard drives total and available space.

  166. Command Line -d: Information logged: Test access to ETL+ metadata - if fails, test access to a test database on the same SQL instance where ETL+ metadata is.

  167. ETL+ Multi-session Mode: When there’s more than one ETL+ Desktop session running with the same entity, each session shows “Other session(s) open: <# of sessions>” on the ETL and Job pages. This feature notifies of other users on the same entity and prevents configuration overwrite conflicts.

  168. Hovering the mouse over “Other session(s) open” message will show the other session’s usernames.

  169. The message above is auto-refreshed every 15 seconds.

  170. This feature monitors open sessions on pages: ETL, Job, Settings, Client Info, and Data Sources.

  171. When one of the sessions saves a change to the metadata, the other sessions will receive a notification that they are outdated. Those sessions turn into a Runtime mode (no ability to change, just view and run loads and scripts), and the Save buttons become disabled.

  172. When a session turns into a Runtime mode, close and re-open the entity to make changes to it.

  173. ETL+ Runtime mode: ETL+ can only execute pre-configured templates, and configure the pre-configured data sources, and job schedules.

  174. ETL+ Limited mode: ETL+ can only work and modify pre-configured templates.

  175. ETL+ admin improvements: Admin users can configure many of the texts used in the ETL+ user interface such as error messages and log descriptions.

  176. When duplicating an entity for Pro and Enterprise, the 99 user can now deploy the Tableau script when saving the Client Info page.

  177. Double-clicking an entity on the Entity list will open it.

  178. When the debug mode is on, the Job Refresh Start log line shows the .NET version installed on the host computer.

  179. Data Warehouse admin refinements: When duplicating an entity, 99 users select the data warehouse prior to filling out the Client Info page.

  180. Data Warehouse key=1 (multi-tenant) is no longer editable via the ETL+ UI (security reasons). 99 users can view it, but not edit it. IT users can edit its settings directly in the metadata database.

  181. Regular users: they can now modify their single-tenant data warehouse settings.

  182. Regular users: from the ETL page, click Settings → Data Warehouse → fill out the data warehouse settings → Save.

  183. When creating a new entity (or duplicating a new one), there’s no need to close it. One can use it right off the bat.

  184. ETL+ Watchdog: A new Linux-based engine to monitor ETL+ processes.

  185. ETL+ WatchDog: Email notification of Job start failures is sent 5 mins from the scheduled start time.

  186. ETL+ WatchDog: Email includes DeviceName, Agent status, Job status, and other metadata info.

  187. ETL+ WatchDog: Email contains a link to open the ETL+ Web Job page with expanded logging.

  188. ETL+ Installer: The new installer easily sets up the DataSelf ETL+ and Agent Service environment in Windows computers.

  189. By default, the ETL+ is installed in the following folder (the user can change the folder):

    1. C:\Program Files\DataSelf ETL Plus

  190. When applicable, the ETL+ saves its working files in the following Log and Working Files folder:

    1. C:\Users\Public\DataSelf

  191. Settings Page: New entry to customize the location of the Log and Working Files folder.

  192. Settings Page: Icon to configure the Log and Working Files folder location.

  193. When applicable, these are the folders that are saved in the Log and Working Files folder:

    1. DS_Credentials

    2. DS_Downdows

    3. DS_SourceFiles

    4. OlderVersions

  194. ETL page: Added Log and Working Files icon on the top right. Clicking it gives you ways to reach that folder as well as the folder where ETL+ is running from.

  195. Job page: Added Log and Working Files icon on the top right. Clicking it gives you ways to reach that folder as well as the folder where ETL+ is running from.

  196. The installer also installs and deploys the new DataSelf Agent Service.

  197. DataSelf Agent Service: Now the Agent runs as a Windows Service.

  198. The Agent is automatically installed and run as a Windows Service upon installing DataSelf ETl+.

  199. By default, the Agent Service runs with the LOCAL SERVICE Windows account.

  200. The Agent can be maintained (stop, start, pause, credentials change) in the Windows Services app.

  201. The Agent local log file has been moved to the Log and Working Files folder.

  202. The Agent now logs: when the service starts and its version.

  203. The Agent now logs: when the service shuts down.

  204. The Agent now logs: successful connection to the ETL+ metadata.

  205. The Agent now logs: if using the default or a custom ETL+ metadata.

  206. The Agent now logs: successful connection to the ETL+ metadata.

  207. The Agent now logs: failure connecting to the ETL+ metadata.

  208. The Agent now logs: date & time when a new task runs.

  209. The Agent now logs: date & time when a new task ends.

  210. ETL+ Web - Beta version: New web UI allows admin users to monitor and make changes to certain ETL+ processes anytime and anywhere.

  211. ETL+ Web: Released for super admin users.

  212. ETL+ Web: User authentication using Azure AD, SAML-based, Single Sign-on (SSO) enabled.

  213. ETL+ Web: User authentication is locked to @dataself.com users.

  214. ETL+ Web: Jobs page created mimicking the equivalent ETL+ Desktop features.

  215. ETL+ Web: ETL Log page created mimicking and improving the equivalent ETL+ Desktop features.

  216. ETL+ Web: Settings page created mimicking part of ETL+ Desktop features.

  217. ETL+ Web: Client Info page created mimicking part of ETL+ Desktop features.

  218. ETL+ Web: A Transfer page to easily exchange files.

  219. ETL+ Web: Users page created to manage SSO.

  220. ETL+ Web: Menu buttons to access ETL+ pages.

  221. ETL+ Web: The menu button has a green background and indicates the ETL+ Page in session.

  222. ETL+ Web: Top-left button shows the Master Entity filter.

  223. ETL+ Web: Top-left shows the selected entity’s data warehouse information.

  224. ETL+ Web: Top-right shows username logged in.

  225. ETL+ Web: Top-right shows ETL+ Web version.

  226. ETL+ Web: Top-right shows ETL+ Web's metadata's SQL instance name.

  227. ETL+ Web - Master Entity filter: Shows a description of the selected entity(ies) and the number of entities when more than one is selected.

  228. ETL+ Web - Master Entity filter: Allows searching.

  229. ETL+ Web - Master Entity filter: Check/Uncheck All icons.

  230. ETL+ Web - Master Entity filter: When a single entity shows on the list, press Enter to select it.

  231. ETL+ Web - RESET FILTER button clears filters to their default values.

  232. ETL+ Web - User page: Contains columns for email, actions, first and last name, token, user key, type, status, default entity, created at.

  233. ETL+ Web - User page: One can sort the page by the page headers.

  234. ETL+ Web - User page: Email search box.

  235. ETL+ Web - Job page: Contains columns for Entity ID - Key, Job, Actions, Agent, Job Status, Job Name, Last Run, Next Run, Load, App.

  236. ETL+ Web - Job page: One can sort the page by the page headers.

  237. ETL+ Web - Job page: Search box for the name of the App running the Job schedule.

  238. ETL+ Web - Job page: Agent column filter with values: Offline, Active, WTS.

  239. ETL+ Web - Job page: Job Status column filter with values: Running, WTS Assigned, ETL+ Desktop Only, Scheduled, Unscheduled.

  240. ETL+ Web - Job page: Load column filter with values: Default, Forced.

  241. ETL+ Web - Job page: Action: Run Job.

  242. ETL+ Web - Job page: Action: Clicking Run Job will prompt confirmation.

  243. ETL+ Web - Job page: Action: Stop Job.

  244. ETL+ Web - Job page: Action: Clicking Stop Job will prompt confirmation.

  245. ETL+ Web - Job page: Action: Job Properties.

  246. ETL+ Web - Job page: Action: Job Properties icon toggles the Properties panel on and off.

  247. ETL+ Web - Job page: Action: Selecting a Job Properties highlights the Job with green.

  248. ETL+ Web - Job page: Job Properties - Schedule toggle icon.

  249. ETL+ Web - Job page: Job Properties - Dropdown for schedule frequency: Daily, Weekly, Monthly.

  250. ETL+ Web - Job page: Job Properties - Weekly options provide checkboxes to run the Job on Sun, Mon, Tue, Wed, Thu, Fri, Sat.

  251. ETL+ Web - Job page: Job Properties - Monthly options provide checkboxes to run the Job on each day of the month from the 1st to the 28th, Last day, Check All, Uncheck All.

  252. ETL+ Web - Job page: Job Properties - Dialog for setting the Job’s Start’s Date/Time.

  253. ETL+ Web - Job page: Job Properties - Repeat task every toggle icon.

  254. ETL+ Web - Job page: Job Properties - Text box for min.

  255. ETL+ Web - Job page: Job Properties - Text box for For a duration of X hours.

  256. ETL+ Web - Job page: Job Properties - Load Type radio button.

  257. ETL+ Web - Job page: Job Properties - Dropdown to select the App to run the Job schedule. Options: WTS and Agents assigned to this Job.

  258. ETL+ Web - Job page: Job Properties - Save button.

  259. ETL+ Web - Job page: Job Properties - Save button enabled only when changes are pending saving.

  260. ETL+ Web - Job page: Job Properties - Closing properties without saving changes will prompt confirmation.

  261. ETL+ Web - Job page: Job Properties - Saving a Job’s Properties will update the Job’s columns Agent, Job Status, Next Run, Load, and App.

  262. ETL+ Web - Job page: Action: Job Steps.

  263. ETL+ Web - Job page: Action: Job Steps icon opens the Steps panel on the right.

  264. ETL+ Web - Job page: Action: Job Steps icon toggles the Steps panel on and off.

  265. ETL+ Web - Job page: Job Steps - Close and Save buttons.

  266. ETL+ Web - Job page: Job Steps - Save button enabled when there are changes to save.

  267. ETL+ Web - Job page: Job Steps - Closing panel without saving prompts confirmation.

  268. ETL+ Web - Job page: Job Steps - HIDE UNCHECKED icon. To hide all rows that are unchecked.

  269. ETL+ Web - Job page: Job Steps - HIDE TABLE icon. To hide all Table rows.

  270. ETL+ Web - Job page: Job Steps - HIDE TABLEAU icon. To hide all Tableau rows.

  271. ETL+ Web - Job page: Job Steps - HIDE CLOUD SCRIPT icon. To hide all Cloud Script rows.

  272. ETL+ Web - Job page: Job Steps - HIDE COMMAND LINE icon. To hide all Command Line rows.

  273. ETL+ Web - Job page: Job Steps - HIDE CSV DOWNLOAD icon. To hide all CSV Download rows.

  274. ETL+ Web - Job page: Job Steps - Move to Top icon. Select rows, and click this icon to move them to the top.

  275. ETL+ Web - Job page: Job Steps - Move Up icon. Select rows, and click this icon to move them one row up.

  276. ETL+ Web - Job page: Job Steps - Move Down icon. Select rows, and click this icon to move them one row down.

  277. ETL+ Web - Job page: Job Steps - Move to Bottom icon. Select rows, and click this icon to move them to the bottom.

  278. ETL+ Web - Job page: Job Steps - Selected Check/Uncheck icon. Select multiple steps and click this icon to check/uncheck their checkboxes in bulk.

  279. ETL+ Web - Job page: Job Steps - Tables Check/Uncheck icon.

  280. ETL+ Web - Job page: Job Steps - Scripts have the Properties icon enabled.

  281. ETL+ Web - Job page: Job Steps - Scripts Properties icon toggles its settings panel on and off.

  282. ETL+ Web - Job page: Job Steps - Clicking the Properties icon of a Script allows one to view and change the script settings.

  283. ETL+ Web - Job page: Job Steps - Drag & Drop Steps position - Select one or multiple steps (use Ctrl or Shift), drag and drop them up or down on the Step list.

  284. ETL+ Web - ETL Log page: Contains columns for Entity, DateTime, Desc, Source Error, Type, RunID, Device/User, Job.

  285. ETL+ Web - ETL Log page: One can sort the page by the page headers.

  286. ETL+ Web - ETL Log page: Search boxes for Desc, Source Error, Device/User.

  287. ETL+ Web - ETL Log page: Center-top: 250 Rows Retrieved.

  288. ETL+ Web - ETL Log page: Change the number of Rows Retrieved and press Enter. Prompt to confirm if the row count to retrieve is over 10K.

  289. ETL+ Web - ETL Log page: By default, the log list is sorted by DateTime where the most recent log row is at the bottom of the list.

  290. ETL+ Web - ETL Log page: Log Desc that is longer than 200 characters will show an icon on the far right. Click the icon to see the whole Desc.

  291. ETL+ Web - ETL Log page: Log SourceError that is longer than 20 characters will show an icon on the far right. Click the icon to see the whole SourceError desc.

  292. ETL+ Web - Settings page: Client Info - shows Entity, Name, Users, Source System, Phone, License dropdown.

  293. ETL+ Web - Settings page: Has an Entity dropdown filter with the entities available from the Entity Master filter. The Setting’s Entity filter can only show one entity at a time. By default, it shows the first of the list.

  294. ETL+ Web - URL parameters: Syntax: https://etl.dataself.com/<page>?parameter1&parameter2&etc

  295. ETL+ Web - URL parameters: <page> can be logs, jobs, users, settings, clientinfo, transfer, and use cmd for commands (like run a Job).

  296. ETL+ Web - URL parameters: ? separates URL from parameters

  297. ETL+ Web - URL parameters: & parameter separator

  298. ETL+ Web - URL parameters: e=<EntityKey> (e.g.: e=12)

  299. ETL+ Web - URL parameters: Sort ascending sort=<ColumnName> (e.g.: e=12&sort=EntityID)

  300. ETL+ Web - URL parameters: Sort descending sort=-<ColumnName> (e.g.: e=12&sort=-EntityID)

  301. ETL+ Web - URL parameters: filter[<ColumnName>]=<Value>, requires e= (e.g.: e=12&filter[Job_Key]=1)

  302. ETL+ Web - URL parameters: Expand job properties jxp=<JobID>, requires e= (e.g.: e=12&jxp=1)

  303. ETL+ Web - URL command: Run Job jr=<JobID> requires cmd?e= (e.g.: cmd?e=12&jr=1)

  304. ETL+ Web - URL command: Stop Job js=<JobID> requires cmd?e= (e.g.: cmd?e=12&js=1)

Fixed Issues

  1. Regular users with multiple entities couldn’t select the bottom 1 or 2 entities. Fixed.

  2. When login into ETL+, regular users with multiple entities had to select the entity 1 or 2 rows above the desired one. Fixed.

  3. When duplication an ETL+ entity, EntityID words between single quotes weren't replaced with the new EntityID. Fixed.

  4. When logged with a regular user, if the ETL+ couldn’t connect to the data warehouse, it would open the 99 user data warehouse configuration page.

  5. Opening an entity that had its data warehouse offline was triggering a large number of log error lines. Now it only shows 3 log error lines.

  6. Converting datetime to date type wasn’t working. Fixed.

  7. Timestamp columns converted to char(23). Fixed.

  8. When opening the Job page, Job ID Steps don't show until selecting another Job on the left. Fixed.

  9. With Providex sources, when linking tables to use a filter from the parent table with Replace, ETL is logging failure because of incorrect column name for the filter name (ex.: H.InvoiceDate). Fixed.

  10. Upon adding a new table from a NetSuite ODBC, the SQL syntax will have an extra ] at the end of the table name. Fixed.

  11. ETL+ delta extractions issues with date filters fixed.

  12. ETL+ sends email even when the feature is set to Cloud notification or No Notification.

  13. Many SQL Statements for MongoDB ODBC will only load using SELECT *. Fixed.

  14. Client Info page: The User’s Email registration button wasn’t working. Fixed.

Known Issues

  1. Replace delta configuration for table joins only accepts MAX(FilterColumn).

  2. Sometimes, the source metadata is deleted. For instance, opening an entity with a prior version and then with this one deletes the captured source metadata.

  3. Upon upgrading an entity, connections to SQL might be set to Windows Authentication.

  4. If adding a zDw SQL View to ETL+, it won’t recognize that the object name already exists in SQL and will allow saving it. If trying to delete the ETL+ table, the UI freezes. Kill ETL+, rename the SQL view, delete the table.

  5. Trying to switch a data source from one type to another crashes ETL+.

  6. When running Jobs, if ETL had a data warehouse connection error, it would switch into a failed load for all remaining job steps.

  7. When running Jobs, a single failure to connect to the data warehouse errors out. The process wasn’t retrying 3 times.

  8. In single-tenant data warehouses where sources are set to customized schemas, 0_UnionID columns might not bring in the correct value. For more on schemas See https://dataself.atlassian.net/wiki/spaces/DS/pages/1818853383/ETL+Source+Drivers#Schema-Checkbox

  9. User actions to run a Job via de UI or Agent weren’t being logged.

  10. Odata v3 extraction from GIs with spaces in their names might fail.

  11. Regular users could open pre-saved 99 user UI in DataSelf domains.

  12. Google Sheets: Issues extracting tables with space or line breaks in column names.

  13. Google Sheets: Issues extracting some tables. You might need to re-load the sheet source metadata and remap it.

  14. Importing a table that was already pre-mapped was duplicating the pre-mapped SQL Statement instead of adding the table from scratch again.

  15. Adding new tables sometimes wouldn’t automatically create their Extract SQL Statment.

  16. Command line -d: Not working as designed.

  17. Running Jobs from Acumatica sources that don’t have their source metadata captured, and Acumatica doesn’t render the metadata, ETL+ Job refresh will hang indefinitely.

  18. When running Jobs and a source’s captured metadata is NULL, ETL+ will load the source metadata.

  19. Excel and CSV mappings would not list all columns in the target metadata.

  20. Upon logging in, ETL+ is not remembering the last open entity.

  21. Agent start is logging as connected to the default metadata even when customized.

  22. Regular users: they can create/save a new data warehouse if their data warehouse is set to multi-tenant.

  23. The Job Status column doesn’t necessarily reflect the status until leaving the Job page and coming back.

  24. Debug OFF still creates a local log file.

  25. When a source doesn’t have its metadata saved, and a table is loaded on the ETL UI, the source metadata load happens without visual feedback. It looks like it's frozen, but it’s not.

  26. Target varchar(n) fields from OData sources are filling up with trailing spaces. This doesn’t occur for varchar(max).

  27. F2 and Rename actions don’t work on Job ID 2 or greater (use double-click instead).

  28. Many tooltips stop working after a source refresh.

  29. Upon upgrading, some installs might incorrectly initiate IP whitelisting. Execute popular fix from ETL+ Installation Troubleshooting.

  30. Sometimes, refreshing the zData Warehouse will not load the list of tables. Close ETL+ and re-open.

  31. With Providex sources, remote ETL sessions can’t open Design nor show delta refresh filters for tables with table linking.

  32. When you need to parse a SQL Statement to build its list of columns, but the Confirm button is not enabled, change the Statement, Confirm, change it back, Confirm.

...