Sign Up for Training |
insightsoftware Company Site
Submit a Request
Become a Jet Insider
Give Feedback

Jet Analytics - Release Notes


Jet Analytics 2020 (20.10.1) 

March 27, 2021

New and Improved Features 

Data Lake-optimized ODX storage implementation including file format change to Parquet

Automatic incremental load from the ODX into a data warehouse

Alerts and e-mail notifications on critical errors in the ODX service

New ODX tab where you can browse the data storage, see information on storage on the table level and select tables for the data warehouse

Data source explorer with functionality for confirming that selection rules, incremental load rules etc. work as expected

Independent synchronize and transfer tasks to make task schedules more transparent

Project lock to prevent multiple ODX servers from using the same ODX project

Safe shutdown of ODX server to make upgrading easier

Improved logging UI and less logging of redundant information

Ability to connect to initializing ODX server from the Jet Analytics application


7021: Unable to remove pending tasks in ODX Execution Queue

7821: SQL Server Logins results in error on Azure SQL DB

8403: SSL: Format string defaulting to Invariant Language

8575: Project variables object null reference when edited without opening the script editor

8606: Business Central adapter: Username and password cannot be changed

8765: Cannot deploy primary key delete SSIS package when the data source is bit specific

8767: 32/64 bit execution engine stalls on deployment and execution when failing on initializing communication.

8811: Data Source Excel leaves out columns with type LongVarWChar - text column with more than 255 characters

8863: Error generating Super Natural Key on SQL Data Warehouse

8889: Oracle slow synchronization - affects all bit specific data sources

8892: Timextender memory leak - an issue on data source explorer

8925: SQL Data Warehouse has slow performance with identity insert, when using insert into a table - Data Cleansing

7884: "Cloud Repository is corrupt" is reported if the ODX is unable to reach the cloud repository

8850: "Specified cast is not valid" exception is thrown when backlog was successfully created but the firewall blocked the request to add a project

8907: Azure Data Factory transfer to Data Lake can give an error: "Token has expired"

8911: Incremental load on decimal datatype is not working

8980: Qlik Sense terminate execution issue

8551: Oracle fails when using date fields as incremental load in ODX on OLE DB version

8907: ADF to ADLG2 token expiry issue

8959: Parquet and datetime2 issue

9017: Execution package with retries can return "Broken pipe" error

9039: Issue with execution package with retries

9033: ODX Parquet transfer can use all memory on large transfers

9118: ODX upgrade issue

9115: Table transfer from ODX to DWH fails when ODX table contains a DWH system field name

8659: Error when opening the errors menu when a table contains Geography data

8719: ODX tab closes on F5 (refresh)

9238: Having a Tag on a field mapped to ODX and ODX synchronizes will cause an error

9259: Issue with setting process affinity for more than 16 cores

8266: ODX Config allows you to enter project names of invalid length

9274: Azure access tokens are sometimes not refreshed and expire after an hour causing transfers to fail

9289: Database cleanup recognizes Semantic Security Table after schema change

9287: Azure access token timeout when transferring from Lake to DWH

9337: ADF SQL source incremental load value loses precision for datetime2 where precision is above 3

9344: Incremental load loses precision for datetime data type when the source is an ADF type

Numerous issues with windows and UI elements, that did not scale correctly with display scaling set to more than 100%, has been fixed. The application should now be fully DPI aware and usable on modern systems that default to a higher display scaling factor.


9428: NAV BC365 wrong conversion of DATE data type

9453: Nav query table - data type varbinary becomes unknown data type

9481: TimeXtender crash if you rename an execution package to an existing name

8969: ODX SAP DeltaQ delta load

9291: ODX get unresponsive when having a lot of execution logs

9457: ODX - temp folder is used for generating file names and will eventually get filled up

9001: Application secret is now obscured in the Global Database settings of the DWH
Application secret in the user dialog for Global Database setting for DWH was in clear text

9538: SQL DWH - Conditional lookup is now correctly cast to the destination data type

The Data Cleansing script for MDW Tables on Analytics SQL Pool was missing an explicit data type cast on conditional lookup fields when the Lookup Aggregate option was set to None. This is important due to the use of CTAS pattern and table switching employed on this specific platform.

9550: Updated logic to support table inserts from views on Analytics SQL Pool
When inserting data into a table from a view the databases on the Analytics SQL Pool platform do not support default values. Therefore the script has been adjusted to include getutcdate() as the value for [DW_TimeStamp] if such a column does not exist in the view.

9539: SQL DWH - Grouped None aggregated conditional lookups would look up the first lookup field for all lookups
The Data Cleansing script for MDW Tables on Analytics SQL Pool with multiple lookup files would only lookup the first field when the Lookup Aggregate option was set to None.

9575: Supernatural keys based on transformed values now works on SQL DWH
The Data Cleansing script for MDW Tables on Analytics SQL Pool has been adjusted to apply custom transformation before applying supernatural keys. Before this, the script would result in an empty insertion.

9596: Custom Semantic Measure dialog can now be resized and maximized
The dialog could not be resized and did not have a maximize option

8778: Improved messages at empty ODX Data Source Sync
Reformulating the system messages when setting up data sources and synchronization to help users take proper action when synchronization returns with empty results. It now includes a hint that filters on the data source could be too restrictive.

9033: Added an option to reduce memory consumption when transferring data from parquet files to SQL MDW through the ODX server
Limit memory consumption by subdividing parquet extraction into multiple column groups.

9291: The ODX can now handle a lot of execution logs without becoming unresponsive
Dialog updated in wrong thread to inform the user of excessive log messages available.

9372: More robust error handling to fix issue with unsuccessful transfers from ODX to DW
Building ODX failure handling more robust in case a data source transfer completed unsuccessfully, leaving the file Model.json in an invalid or missing state. The new routine will try to reestablish the old file or seeking out the last working version of the data source before the failed transfer.

9556: Improved incremental load on ODX to work with string data type
ODX generated extraction script now applies the right MAX criteria to the query when extracting an incremental load based on a string data type. This would generate empty extractions previously.

9561: ADF Date datatype and Synapse transfer error
ODX now identifies Date types as a native parquet data format and generates the proper table format for Polybase transfer in Analytics SQL Pool MDW.

9580: ODX can now creating a parquet file larger than 2GB
The variable containing the file position of the parquet file when we upload the data is an integer, but should be of type long. This meant that a file larger than 2147483647 bytes would overflow to a negative value and the upload will fail.

8537: Improve display of very large custom transformations etc.
Very large custom transformation is now handled in the user interface to ensure a fast and stable workflow. This is done by limiting the quick tooltips.

9442: Faster repository loading through the dialog for administration of repositories
The script for fetching the repositories and matching versions have been optimized to allow for faster retrieval and the general timeout setting for the repository has been added to this command execution too. This will allow even larger version history to be easy to load and maintain in the dialog.

9456: Optimizing the appearance of the dialogue Get Stared
With certain display setting the dialog would appear exceptionally large. This is optimized to ensure at more proportional displaying.

9603: Fully qualified names in Custom measure script in Shared Semantic Access Layer
In some instances the fully qualified names was not displayed in the custom measure scripts even though it was set to do so. This has been improved to handle these instances and insure the proper code is generated for the endpoint.

9654: Improving data cleansing script generation for custom transformations
The situation with similar column names in lookup tables could generate invalid transformations scripts for databases running in Synapse Analytic SQL Pool. Proper aliasing is now applied to the script to allow for this situations to be handled safely too.

9658: Any source OLE DB and Any source ADO - improved adding and editing filters
In some cases adding and editing filter models on this data source would not save the changes. This is now improved to safely capture all your changes.

9659: Removed a programming glitch from Resume Execution feature
Updating the UI produced an error that effectively make resume execution impossible to perform.

9691: Drag and drop fields now supported for Data Export tables
You can now drag and drop fields in the selection rules dialog

9695 Adjusting dialog input to actual field sizes
Input validation have been adjusted to ensure proper data length and eliminate issues due to overflowing in some extreme case.

9708: DB/2 data sources (IBM Managed) would produce error when trying to connect.
This have been changed to avoid unnecessary connection attempts that would result in errors.

9725: Updating a project variable refreshes displayed custom transformation automatically
When a custom transformation on a table field uses a project variable a value change in this variable is now instantly displayed in the user interface for this custom transformation.

9726: Allow long running cleanups of old metadata extractions
On large data sources with the application now allows the clean up process to be performed without timing out and producing an unspecified error.

8504 Added extra info on dialog for Scheduled Tasks
The name of the data source have been added to help the user identify the individual tasks in the dialog. This have become even more relevant now that the requirement of uniqueness for task names have been lifted.

9663 ODX supports passthrough of data type Real
Using ADF to populate the data lake now supports the data type Real natively in Parquet files. This makes it possible to move this data type directly in to Synapse Analytics SQL Pool via Polybase for high throughput cases.

9816 Support translations for NAV adapter using BC365 connector
This new functionality will provide translations in a user defined language for table names, field names and option values

7265: New UX behavior when setting hash distribution column for DW in Synapse SQL pool (SQL DW)
The logic for automatically setting a column for HASH distribution will skip DW_ID as default because identify columns are not allowed for HASH distribution.

8262: SQL script editors now also recognize min() function
For code markup the min() function will now show up in the proper color in the code editor.

8449: New icon for tables running in simple mode
The icon is now aligns with the current UI styling
9884: Stabilized ODX to DW transfer
When Jet Analytics moves data from a ODX Data Lake to the MDW using ODX for the transfer, having a selection rule on incremental data, and update/delete, then the the operation could fail due to an attempt to delete a temporary table twice.

Jet Analytics 2020 (20.5.5) 

July 2, 2020

New and Improved Features

BC Cloud Connector App Extension

Name change: Discovery Hub => TimeXtender

32-bit data sources in 64-bit Discovery Hub

Ability to Customize Decimal Scale In Numeric Fields

Simplify "Import Settings from Previous Versions"

h Syntax Highlighting and Autocompletion

Allow related records to be inserted from a view

Easy Way to Create Table from View

Improve Drag and Drop Creation of View from View

Improve Map Custom View Fields

Consistent use of DW_Sourcecode in views

Multiple running scheduled packages from the same project

Split Incremental load marker on multiple sources

Enable incremental load with 'Add Incremental Selection Rule'

Ask the user to synchronize after making a change to a data source that requires synchronization

Show cardinality on semantic relations as arrows (e.g. ->)

Allow manual assignment of system fields on table insert

Drag a field from the Data Movement to Table when Source is ODX

Show schema on external business unit tables

Multiple text file Data Source - Add filename 

Deprecated Features

Download of 32-bit version of TimeXtender

TimeXtender Client version

Fixed in 20.5.1

2848: Version note canceled Execute still runs

4411: Project load slow due to external executable projects

4564: UI: "Synchronize Data Types" is placed differently in context menus on table and data warehouse

4637: UI: Missing padding in "Set Up Relations" dialog box (req. Infragistics upgrade)

4675: Issue with SSIS and differential deployment

4766: The Automate Incremental load feature on the DWH adds incremental load to tables where this isn't possible

4831: Custom conditions on any field transformation reference fields in the _R table and ignore transformations on these fields

4995: Verify and update the prerequisites page on

5286: Issue with retry in an execution package with multiple packages inside

5315: Primary key null check combined with rec.based validation

5327: To improve deployment performance, _RT table hash columns should be nullable

5359: Data linage down to the data source is not possible

5464: "{" and "}" characters in object names fail in Azure SQL

5506: Error when you turn off using a partition on a table.

5559: Window closes when the tab is closed

5768: SSL - Removing a column and the affected in semantical model

5805: Expire date in About dialog is misleading if you have a subscription license

5822: Aggregate table override data type is applied wrong

5891: Data type override should not be available for additional data sources.

6098: Hourglass overlay is displayed when nothing is deploying/executing

6119: Export deployment step issues when creating documentation
table containing decimal fields.

6213: Object reference error after an upgrade, when synchronizing external SQL data source

6227: Custom view fields are not reordered after synchronizing fields

6229: Reordering table fields "is dirty" issue

6248: Execution package messages on manual stop issue

6350: Data Source with additional source and history doesn't do data cleansing when one source fails

6382: Issue with SQL Database Cleanup Tool

6383: UI: 'Max. rows to copy' label is misleading

6423: Change a data source from X type to SAP data source more than once fai

6443: Change data source to Movex/M3 DB2 and Movex/M3 MS Sql Adapter fails

6463: AZDWH Bulk load data conversion error - Polybase to Azure SQL DWH

6494: Issue with missing fields from CData providers

6496: Performance recommendations suggest aggregation None for lookups when the target is SQL Data Warehouse

6607: Error with data conversion from NVarChar(MAX) field

6636: Ampersand & sign bug in the project name

6638: Version counter bug

6801: Issue with creating roles in ODX security

6859: Query table with fields without a name

6864: Polybase with primary key load from fixed value fields

6872: Issue with moving data with polybase and "copy to" when preview data exists

6908: Missing fields for mappings in custom selection rules

6925: Deployment through multi-environment window fails when using Azure Analytics Services and deployment mode is automatic/universal.

7044: Add data source any CTRL+E

7051: Execution fails when mapping dw_sourcecode from business unit to data warehouse

Fixed in 20.5.2

6908: Missing fields for mappings in custom selection rules

7491: Issue with advanced settings in a CData provider

7515: First run keeps showing up

Fixed in 20.5.3

7589: Data warehouse: default values for Data Factory settings when using a global database are incorrect and fail when the global database does not exist.

7576: Wrong cast when using direct read with column default where source field data type is different than the destination field data type

7594: Issue with ODBC connection pool when using NAV Native on Business Central adapter

Fixed in 20.5.5

7600: Issue with field mappings in Semantic measures

7628: Issue with 32/64 bit execution engine which stalls when running the scheduler and multiple threads.

7659: Remote SSIS package execution only works for SQL 2008.

Jet Analytics 2020 (20.1.7) 

May 8, 2020

This version of Jet Analytics has been validated and works with Dynamics 365 Business Central Release Wave 1 (BC16).

Fixed in 20.1.7

6883: Dynamic security doesn't work as expected

6891: OAuth settings file path translation error

6902: Tabular thousands separator isn't checking for 0 decimals

7125: Issue with huge OLAP cubes with many dimension relations causing Jet Analytics to crash hard

7126: Fix UI update issue with huge OLAP Cubes

7151: Issue with analysis services on prem 2017

7154: Issue with SQL 2017

7185: Issue with NAV adapter BC wave 2

7187: ImageCache to improve project load 

Fixed in 20.1.6

Bug 6545: Aggregation table custom selection shows wrong fields

Bug 6608: SSL Perspective not created for enterprise64 edition

Bug 6618: Tabular relation on custom fields not possible

Bug 6857: Error when applying write-back on cubes for roles where one or more measures is in the Denied Set

Fixed in 20.1.5

BUG 6345: Decimal datatype converted to currency for tabular

BUG 6455: Collapsing node when move then with ALT Up/Down

BUG 6458: Slow rename of field used in an OLAP server

BUG 6460: Cannot create repository in empty database on SQL DB

BUG 6361: Custom fields isn't visible in measures with Tabular endpoints

BUG 6465: Issue with Qlik (deprecated) not cleaning up datafields on delete

Jet Analytics 2019 (19.11.7) 

December 23, 2019

      Fixed Dynamic project variables fail when a variable contains quotation characters
      Fixed Deployment of a table makes calls to SMO which requires more user rights
      Fixed Tabular Model not dependent on RLS security table
      Fixed Additional Connection String property dialog can only hold 255 characters
      Fixed issue where JDM wouldn't properly sync with BC Wave 2 data sources. 
      Fixed issue where the Advanced Dimension Editor wouldn't correctly work with BC Wave 2 data sources.

Jet Analytics 2019 (19.9.1) 

October 2, 2019

      Added support for Azure AD Authentication for SQL Server Connections.
      Issue with supernatural key as PK and source-based incremental load with hard deletes.
      Incorrect automatic index for lookups with TOP and sorting
      Preview of some Dynamics AX tables in data source fails
      Copy repository dialog not in line with current GUI
      Money, Smallmoney and XML fails when using ADO without overwriting datatypes
      First run proxy issues Dynamics NAV - Query table for company with ' (quote) in name gives malformed T-SQL
      Encrypt connection not read when opening project repository settings
      Opening and closing tabs should keep the size of existing tabs
      External business unit will display wrong connection changes during synchronization when using a global database
      SQL Azure Data Export encryption error
      Some settings are not imported when a previous version is selected on first run

Jet Analytics 2019 (19.6.8) 

September 4, 2019

      Fixed issue when generating Documentation with Hierarchy Table.
      Fixed issue where wrong Icons were used for Hierarchy table levels.
      Fixed issues with Standard Views.
      Fixed issue where SQL engines ignore some server compatibility settings.
      Fixed first run issue when setting up the repository.
      Fixed issue where Custom Semantic Layer Measures hidden property is not saved.
      Fixed issues for SQL Database Cleanup Tool grouping all independent objects under "Tables".
      Fixed issue where deploying changes takes a lot of time on step "Building Cache”.
      Fixed issue to implement faster opening of tabs.
      Fixed issue with Performance Recommendations: Include orphan Entire Row Hash Key fields.
      Fixed issue when deploying views - index out of range exception.
      Fixed issue when opening an earlier version of a project where NAV and AX adapters are loaded incorrectly. 

Jet Analytics 2019 (19.6.5) 

August 6, 2019

Redesigned User Interface

The most striking feature of the 19.6 release is no doubt the redesigned user interface. Over the years, we have received a lot of suggestions for improvements, and in this release, we have implemented changes that we hope will address the most important ones.

  • Flexible Tabs
    In the new user interface, tabs are no longer static. You can open the objects you want to work with, for instance a data warehouse or a semantic model, in separate tabs side-by-side and drag tables from one tab to the next. Tabs can also be organized in tab groups to give you a better overview of your work.

    What tabs you have open is saved, so the next time you open a project, you can pick up where you left off.

    With flexible tabs, the UI makes much better use of the width of the application window. The “trees” in the various tabs will also be shorter, since you do not have one or more data warehouses and business units in the same tab.

  • Solution Explorer
    In the new UI, all the top-level objects in your solution are listed in the Solution Explorer, which is always displayed in the left side of the application window. From this list, you can open individual objects in tabs.

  • Warnings and Errors in the Reports Menu
    In the old UI, the Warnings and Errors tabs were the odd men out among the other tabs. Because of this, they have been promoted to menu items in the new Reports menu. The menu also includes the execution queue log.

  • Start Tab and Other Changes
    When you open JDM 19.6, a Start tab helps you get started with helpful links to e.g. recent projects. We’ve also added a fresh set of icons, consolidated stored procedures, user defined functions and script actions under a common ‘Script’ node and tweaked the toolbar and status bar to match the other changes

Data Warehouse Layer

  • Show Join for Lookup Fields using the Default Relation
    On conditional lookup fields, the individual lookup fields default to using the default relation between the source and destination table as a join if you have not explicitly added a join. In previous versions of the JDM, there was no indication whether the default relation was implicitly used as a join or the lookup field did not have a join at all. To make this behavior more visible – and thus, more useful – the new release includes a “read-only” version of the join icon that is displayed when the default join is used.

  • SQL Database Cleanup Tool Improvements
    We have added some small improvements to the tool that helps you clean up your project databases. The basic functionality is the same, however. The tool creates a list of tables and scripts in a data warehouse or staging database that are not part of the current project and gives you an option to delete them.
    You can now run the tool on the project level to clean up all databases in the project in one go. In addition to that, the list of objects now uses display names and icons to make it easier to read. Lastly, the tool is no longer called a “wizard” since that was rather misleading.

  • Keep Lookup and Supernatural Key Field Values Up-to-date
    One of the challenges of using incremental load is that the value of a lookup field on an incrementally loaded table does not change if the value being looked up changes. The lookup field value is calculated when the row is loaded so the usual solution to this problem is to schedule regular full loads of the table.
    In this release, we have added a new setting on incrementally loaded tables, “Keep lookup values up-to-date”. When this setting is enabled, JDM will do comparisons to see if any values being looked up have changed and will update the lookup fields accordingly.
    The new release includes fixes and improvements to the feature that brings it out of beta. Supernatural key fields are now also kept up to date if you enable the feature. At the same time, an issue in the logic that would trigger unnecessary full loads, has been fixed.

Shared Semantic Layer

  • Hide Measures in Semantic Models
    Hiding a field or measure in a semantic model can be very useful if you, for instance, has a custom measure referring to an intermediate field or measure that you do not want the end-user to see in the front-end. You have long been able to hide a field on a table and in the new release, we have added the option to hide a measure as well.

  • Improved Authentication for Azure Analysis Endpoints
    The new release adds new authentication options for SSAS Tabular endpoints. Previously, the user account executing the endpoint would always be used to authenticate with the server. In the new version, we have added two additional options for authentication. You can enter the username and password for the account you want to use or create a service principal in Azure and user that for authentication.

Deprecated Features

  • 'Advanced Options' Display Setting
    The Advanced Options setting on the View menu has been removed. The option controlled the display of advanced options, but it was enabled as default and there was little reason to disable it. Therefore, we decided that it was superfluous.


Jet Analytics 2019 (19.2.9) 

June 10, 2019

  • Fixed issue where the Informix date-time format for incremental rule would use the environment date-time format.
  • Fixed issue for when Simple mode on data source would not clean up pre and post steps
  • Fixed issue where Azure SQL would not work in ODX
  • Fixed issue where a Wrong Mail error mail could be sent by the scheduler
  • Fixed issue where OLAP translations were not deployed with Discovery Hub Feature


Jet Analytics 2019 (19.2.5) 

April 29, 2019

Data Warehouse

  • Performance Recommendations
    As we continue to develop the Jet Data Manager, we add new options and features that improve performance.

    For instance, the 18.10 release included significant performance improvements for conditional lookup fields

    In the new release, we have included a feature to help you take advantage of these improvements with only a few clicks. With performance recommendations, you are presented with a list of possible optimizations and a list of the affected objects. You can deselect any optimizations you do not want to apply, but otherwise, you just need to click OK and deploy your project to improve execution times.

    While we could just enable the options and features that improve performance automatically, we take a cautious approach to rolling out the new features. New projects will default to using the improved settings, but we will not change settings in existing projects.

  • Improved Performance for Incremental Load and History Tables
    One of the major advantages of using the Jet Data Manager is that improved performance is just a deployment away when we optimize the code generated by the platform. This release includes performance tweaks to incremental load and history. Especially for tables with history enabled, the gains are substantial. In our tests, history-enabled tables execute about twice as fast as before - or even faster. However, we cannot guarantee performance improvements on that level in all cases since it very much depends on the complexity of the table.

  • Data Lineage for Custom Views
    In the new release, you can map the ‘input’ and ‘output’ fields in a custom view to enable tracing all the way from data source to semantic layer. This information is used both in the visualization options in the software as well as in the documentation it generates.

    In previous versions of the Jet Data Manager, a custom view would create fields ‘out of the blue’, since the Jet Data Manager cannot automatically map fields from data sources to the fields created by a custom view.

Shared Semantic Layer

  • Dynamic Row-Level Security
    In the new release of the Jet Data Manager, you can set up row-level security on models in the shared semantic model based on the contents of a data warehouse table. With this feature you can have a single role that grants access to all domain users and then differentiate what the individual user has access to by supplying a table the contains information about the user and data relationship.

  • Add Descriptions for use in SSAS Tabular
    You can now add descriptions of tables, fields and measures in a semantic model and deploy them to SSAS Tabular endpoints. The descriptions are useful for helping end users understand the data in Power BI.

  • Support for Perspectives on SSAS Tabular
    Perspectives can improve the user experience of a complex model for the end-user by hiding the tables, fields and measures the user does not need. You can now add perspectives to semantic models and deploy them to SSAS Tabular endpoints.

Deprecated Features

Due to the improvements to incremental load and history logic on tables in the data warehouse, some settings on tables has been deprecated:

  • Enable BK hash key (Table Settings -> Performance tab): Enabling history on the table will create a similar hashed version of the business key, should you need it.

  • Target-based incremental load (Table Settings -> Data Extraction tab): Enabling history on the table will give you the same benefits with identical performance.

  • Use left outer join (Table Settings -> History tab): This option had very limited use for troubleshooting, but with the new logic, there is no longer any use for it.


Jet Analytics 2019 (18.10.9) 

January 2, 2019

  • Fixed issue where Culture settings on Text files were ignored in global databases
  • Fixed issue with cloning varchar Conditional Lookup Fields
  • Fixed issue where older versions of CData sources were required to be installed
  • Fixed issue where Performance - Security model saved the "none" values to the repository
  • Fixed issue where the wrong table name validation was applied when using simple mode


Jet Analytics 2019 (18.10.8) 

December 6, 2018

  • Jet EULA updated
  • Fixed issue where the entire Row Hash Key would be a primary key
  • Fixed issue where the eeployment of primary key SSIS package would fail when using the providers Oracle Data Provider for .NET and Microsoft Oracle Data Provider for .NET
  • Fixed issue in the AX Adapter where Incremental load with delete would not work with the Account exclude option
  • Fixed issues where the template NAV Adapter would not be affected by changes to the enhancement settings on the main adapter
  • Fixed issue in the AX adapter where Incremental load with subtracting would not work when the account setup was set to exclude
  • Fixed issue with the parsing of default code page in the text file data source
  • Fixed issue where the NAV Cleanup wizard would suggest to remove the necessary Option BCV view


Jet Analytics 2019 (18.10.6) 

November 12, 2018

  • Scheduler now logs errors and warnings to event log, regardless of the configuration setting.
  • Fixed issue where the Up-to-Date option for Lookup Values would fail to deploy.
  • Fixed synchronization issues with the Excel data source.
  • Fixed issue where datasource settings were detecting false changes when changing tabs
  • The AX adapter now using the MS SQL provider from AX7


Jet Analytics 2019 (18.10.3) 

October 23, 2018

  • Fixed issue where Direct Read and Dynamic Variables were not working
  • Fixed issue where batch data cleansing was not working properly with Keep lookup values up-to-date
  • Fixed issue where semantic layer custom measures were not using correct setup type
  • Fixed issue where custom selectionrule in SSL could not handle renaming of parameter field
  • Fixed issue where SQL cleanup wizard was removing security table for semantic layer row security
  • Fixed issue regarding SSIS, Dynamic Project Variables, and Data Selection Rules on Incremental Tables


Jet Analytics 2019 (18.10.2)

October 5, 2018

  • Fixed an issue where the entire Row Hash Key was not disabled
  • Fixed an issue where Aggregated fields would not get marked as modified when source fields were renamed
  • Fixed an issue where a Super Natural Key field would not be available in an aggregation table
  • Fixed an issue with creating new fields after enabling 'Keep lookup values up-to-date'
  • Fixed an issue with CData where REST provider would not be available in the add/edit CData provider
  • Row level security is allowed on semantic customer fields
  • 'Keep lookup values up-to-date' detects changes regardless of case-sensitivity collations
  • Selecting database collation can now be done before creating a business unit or data warehouse database


Jet Analytics 2019 (18.10.1)

October 1, 2018


Feature Description  
Azure SQL Database Managed Instance

This release entirely supports Azure SQL Database Managed Instance, that represents fully managed SQL Server Instance hosted in Azure cloud — allowing customers to easily take advantage of new technology when released by Microsoft. In fact, 18.10 supports any of Microsoft SQL Servers, be it Microsoft Azure SQL DB Managed Instance, Single or Elastic Pool and of course the on-prem SQL database. We recommend MI, but if performance and refresh rate are less important, Single or Elastic pool are also an option

Shared Semantic Layer

Row Level Security
In version 18.10, you can set up row-level security on models in the shared semantic layer. The security setup can be deployed to SSAS Tabular Endpoints.
Controlling access to data on the row level can be a very useful addition to controlling access on the table or model level.  One common example is a sales department where each salesperson needs access to data from their own sales region, but not everyone else’s.


In Jet Data Manager 18.10, you can order fields on semantic layer tables in hierarchies. All endpoint types support hierarchies.

Data Formats

You can now configure data formats and categories on fields which will be applied to SSAS Tabular endpoints and used in front-ends to decide how to display data. For instance, text categorized as “Web URL” can be displayed as a link.

Display Folders

“Display folders” is a feature of SSAS Tabular which allows you to organize the fields, measures and hierarchies of a semantic table by adding them to folders.  This makes the model easier to browse, especially if it has a lot of fields.  With display folders, you can (for example) bucket all address information on a customer table in a “Geography” display folder.

Prevent Deployment of an Endpoint in Specific Environments Jet Analytics v18.10 includes the ability to set an endpoint as inactive in specific environments.  This makes it easier to manage endpoints and prevent overriding production endpoints during development.  
Guarding Semantic Models can now be guarded for deployment and/or execution.  
Prioritize Models on Execution

In version 18.10, Semantic Models can now be prioritized in the execution engine, which gives the user an option to influence the execution order to get certain items finished earlier than others.

Clone Field

Jet Analytics 18.10 includes new context menu command "Clone field" on all fields, as well as a new dialog for cloning fields (incl. Conditional Lookups, Supernatural Keys, Custom Hash Fields, transformations, standard data fields).

Two options appear in the dialog: Cloning structure (incl. transformations) or data (only adding transformations for cloned data).

Consistent Read on Dynamics NAV Adapter

When you extract data from a data source that is in use, you can end up with inconsistent data where a foreign key in a record points to a record in another table that does not exist.

Jet Data Manager 18.10 can use the fact that Dynamics NAV has a timestamp on every table to minimize this problem. If you enable the new consistent read setting, the JDM will only extract records older than the start of the data extraction.  This will prevent inconsistencies caused by data added while extraction is running.

Keep Lookup Values Up-to-Date on Incrementally Loaded Tables

One of the challenges of using incremental load is that the value of a lookup field on an incrementally loaded table does not change if the value being looked up changes. The lookup field value is calculated when the row is loaded so the usual solution to this problem is to schedule regular full loads of the table.
Jet Data Manager 18.10 includes a new setting on incrementally loaded tables: “Keep lookup values up-to-date”.

When this setting is enabled, the JDM will do comparisons to see if any values being looked up have changed and will update the lookup fields accordingly.

Improved Oracle Data Source

Version 18.10 contains improvements to the Oracle data source, which makes it easier to set up the connection and makes the connection Oracle-version independent.

The data source connector now supports EZConnect which means that you can simply enter the connection information (server, port and service name).

More Information on Tooltips Tooltips are now on all fields with information on Transformations. Tooltips on lookup fields will now show information from the lookup data field, joins, conditions, etc. and there is an improved tooltip on conditional lookup fields.  The tooltips react to all relevant changes to fields and relations, always showing up-to-date information, and are now shown for 30 seconds.  
Conditional Lookup Performance and Usability Improvements

New features:

  • When dragging and dropping fields, a new easy-to-use dialog for adding relations is shown, displaying existing relations with a tooltip, possibility of extending an existing relation, or adding a new default relation or non-default relation.
  • When adding a new conditional lookup field or a new lookup field, a new simplified, comprehensible dialog for adding lookup joins is shown, with a possibility of copying joins not only from relations but also from existing lookup fields.  This dialog also shows details of all joins in tooltips.  Only different joins from existing lookups are shown (duplicates are removed from the list).
  • Dragging and dropping of fields in another table with the right mouse button creates a new conditional lookup field instead of a new relationship and allows for easy positioning of the conditional lookup field before or after the dropped field.
  • In the Add/Edit Lookup Field dialog, you can now select which Operator you want to “Set as Default”.
  • New lookup operator 'None' greatly improves performance in some scenarios + automatic changing (after confirmation) of the lookup operator to 'None' when adding joins different than 'Equal'.
  • In the “Add Join” dialog, new lookup join fixed value operators have been added: 'In list', 'Not in list', 'Like', 'Not like'.
  • Copying Lookup Fields within the same table via drag and drop (the right mouse button also offers two options: add or replace)
  • Copying Lookup Joins within the same table via drag and drop (the right mouse button also offers two options: add or replace)
  • Copying Lookup Sortings within the same table via drag and drop (the right mouse button also offers two options: add or replace)
  • Copying Lookup Conditions within the same table via drag and drop, also between lookups and transformations, and vice versa (the right mouse button also offers two options: add or replace)
  • Automatic renaming (after confirmation) of lookup fields and conditional lookup fields when the lookup data field is changed



Performance Improvements:

  • Batch data cleansing now works for all conditional lookups and supernatural keys.
  • History tables have been optimized and work significantly faster
  • Conditional lookups can be merged, so all lookups are performed at one time.


  • The first relation is automatically created as default, and it is no longer possible to remove default from a relation other than by adding default to another relation or deleting the relation.  If there are several relations, one is always default.
  • Creating relations by dragging and dropping fields is now possible also if a relation was already created in the opposite table. Relations now work regardless of in which table they were created, i.e. they can be used in both tables.
  • There are now consistent dialogs for adding/modifying conditional lookup fields, lookup fields, lookup joins, and lookup sortings
  • Lookups now allow MAX and MIN with the bit data type


Jet Enterprise 2017 (17.12.15)

  • Fixed an issue where a Selection Rule on a field in a Table Insert would cause an object null reference
  • Fixed an issue with connection string properties for Dynamics AX and Dynamics NAV


Jet Enterprise 2017 (17.12.14)


Overview of the Improvements in Jet Enterprise 2017 (17.12.14)

Jet Enterprise 2017 (17.12.14) introduced a number of important  modifications. Below is an introduction to the changes made in this version of Jet Enterprise.

  • Added deployment target from SQL 2017
  • an now deploy to or list project repositories on SQL 2008s
  • Table menu in sub tree view window now displays all available menu items
  • Supernatural Keys and Custom hash fields work with Custom Data insert order
  • Deploying dynamic perspectives no longer include OLAP steps without being selected
  • Better deploy validation on partition feature
  • Keep Errors and Warnings on adapter table
  • Corrected the Execution Error Message from the Execute Queue
  • External BU - Synchronized tables with schema changes are now saved
  • Synchronize source field - addressed a conditional lookup field join issue
  • Addressed an AX Synchronize tables issue
  • Transformation - correct the SQL when using reverse sign
  • Execution queue now includes the correct default package logging
  • Simple table mode deploy works correctly when script all objects is checked in deployment dialog
  • Views - addressed a table insert check on dynamic project perspectives issue
  • Application no longer crashes when using perspective
  • Data source multiple text file works properly when using a global database
  • Add DWH/BU dialog correctly displays setting for ssis transfer
  • Addressed an unexpected shutdown of JDM when pressing Ctrl+C in errors or warnings tab
  • No longer duplicates transformations when data movement is loading
  • Addressed a synchronize AX adapter culture issue
  • Table settings do not freeze on edit
  • Opening multiple environment transfer is faster
  • Addressed Import custom data field name issue
  • Addressed warning when comparing hash fields and supernatural keys with an incompatible data type length
  • Addressed an issue with merging of conditional lookups with custom conditions
  • Addressed a problem with conditional lookups using custom fields with transformations containing other conditional lookups
  • Better description of how Simple mode table behaves when the data source is set to continue with data.
    Address a lock-out problem with proxy settings
  • Address an ADO.Net error
  • TABLOCK is now available on update of Key Store
  • Execution package - address an exclude OLAP server with offline processing issue
  • Views no longer have dependencies to data cleansing stored procedures
  • The "Find" dialog now sorts results
  • UI: Tab icons have the correct color depth
  • Partition table on SQL version that doesn't support table partitioning no longer results in error during index creation
  • Addressed an issue with modified tables for color blind people
  • Addressed a issue when sending to the execution queue
  • Edit staging database and data warehouse sets the SSIS Server value.
  • Addressed a Remote SSIS Package Path Issue
  • Addressed an table name issue when synchronizing AX adapter culture
  • Execution Package is now cleaned up when deleting Semantic Model Objects
  • Drag and drop now includes a default action
  • Added transformations on Supernatural key
  • Added Case-insensitive supernatural keys and hash fields
  • History enabled table with reincarnation of data combined with SHA-2 512 Hashing no longer causes error
  • Multiple environment can now connect to versions before 17.12.9
  • Clicking in un-synchronized NAV data source no longer causes a crash
  • Additional AX adapter - Loading primary keys from parent source
  • Go to Source table for views is now working
  • TXStringDateConverter handles invalid dates. (SQL 2005, 2008,2012,2014,2016,2017)
  • Project environment transfer refreshes the project information for the destination environment.
  • Having many versions of a project in remote environment no longer makes the transfer available


Jet Enterprise 2017 (17.12.05)


Overview of the New Features and Improvements in Jet Enterprise 2017 (17.12)

Jet Enterprise 2017 (17.12) introduced a number of important new features and improvements. Below is an introduction to the changes made in this version of Jet Enterprise.



Feature Description KB Article
Support for SQL Server 2017

Jet Enterprise v17.12 supports SQL Server 2017.

Data Tagging

Jet Enterprise v17.12 enables you to tag individual fields. These tags can then be used in project perspectives or in a new type of documentation, data impact - allowing you to better categorize your data and comply with regulations such as the General Data Protection Regulation (GDPR).

Data Tagging
Visualization Possibilities with the Relation Diagram

Jet Enterprise v17.12 includes a new Project Perspectives: The relation diagram. You can view the relation diagram for each table -showing you the tables that have a relation to the table in question.

Project Documentation in the Jet Data Manager
Uniquely Identifying Records with Durable Supernatural Keys

In Jet Enterprise v17.12, we have added the supernatural key as a field you can add to a table - providing a very useful feature for dimensional modeling

Uniquely Identifying Records with Durable Supernatural Keys
Reading SQL Server Synonyms

In SQL Server, synonyms are a simple, but powerful feature.

Jet Enterprise v17.12 includes the optional functionality to read synonyms from the data source.

Customizable and Comprehensive Documentation Jet Enterprise v17.12 includes more options for customization and content for the auto- generated project documentation.  
Flexible Data Selection in Data Warehouse In Jet Enterprise v17.12, data selection rules are defined on the source table level - making them more flexible. Creating a Data Selection Rule
Push Execution to Queue and Skip the Waiting

In version 17.12, Jet Enterprise better integrates the execution queue with the regular deploy/execute flow.

Using the Data Selection Queue




Jet Enterprise 2017 (17.5)


Overview of the New Features and Improvements in Jet Enterprise 2017 (17.5)

Jet Enterprise 2017 (17.5) introduced a number of important new features and improvements. Below is an introduction to the changes made in this version of Jet Enterprise.


Feature Description KB Article
Redesigned Interface

The first thing you’ll notice when you open the 17.5 release is a new and improved user interface. With the redesign, the interface is less cluttered and gives more room to what matters: your data

Internet Connection through Proxy Server

With the wide use of web-based data sources, more of our customers are likely to be using proxy servers.  Jet Enterprise 17.5 now supports the use of a Proxy Server for web traffic.

Support for Internet Traffic through Proxy Server
Support for SQL Azure

Jet Enterprise 17.5 introduces support for using Azure SQL Server for your repository, data warehouse, and staging databases

Using SQL Azure For Repository, Data Warehouse And Staging Databases
Improved Conditional Lookup Fields

The performance, behavior and usability of Conditional lookup fields (the feature that allows you to use a field from one table on another) has been substantially improved.

Converting Older Conditional Lookup Fields

Adding a Conditional Lookup Field

More options for delete handling In JDM 17.5, you have more options for tracking records which are removed from history-enabled tables. More Options for Delete Handling
Type "0" fields now supported Jet Data Manager 17.5 includes support for type 0 fields - which are ignored by the JDM. Use Type 0 Fields on History-Enabled Tables
General Usability Improvements

In addition to the redesign of the interface, Jet Data Manager 17.5 contains a myriad of smaller improvements to improve the usability.

See below
Deprecated Feature Support Some older features in the Jet Data Manager have lived out their usefulness and continue to exist in the product solely for backwards compatibility. While backwards compatibility is a high priority for us, such features will now included the suffix
"(deprecated)" to help you manage your use.

Feature Deprecation

(see below for details)

Improvement to the AnySource Adapter In SSIS packages created by the AnySource Adapter, the TruncationRowDisposition setting is set to RD_IgnoreFailure. This is the same behavior as, for example, the DB2 data source



General Usability Improvements in version 17.5:

In addition to the redesign of the interface the new release contains a myriad of smaller improvements to improve the usability of the Jet Data Manager:

The Automate wizards introduced in Jet Data Manager 17.1 have been tweaked a bit. One-level lists are now proper lists instead of trees which makes multi-selection possible. You will now get a message if the wizard has nothing to show instead of an empty wizard. And lastly the wildcards you can use in the filter are explained in a tip when your mouse is over the filter box.

The Find window has an improved layout and now supports the same wildcards as the filter function in the Automate wizards.

We have streamlined the delete confirmations to give them a consistent look and behavior. On routine confirmations (such as deleting a field or table) the default action is to delete the object. On objects where the impact is bigger (data warehouses, OLAP cubes, etc.) the default action is not to delete the object.

We have improved the warning message you see when you set a timeout setting to 0 on a data source so it is easier to understand. Jet Data Manager shows the warning message since 0 equals infinity in this context which can cause issues if the data source is not responding.

Previous versions of Jet Data Manager would show an unnecessary warning message when you set up Related Records or Table Inserts. Jet Data Manager 17.5 includes a check to make sure the warning message is only shown when appropriate.

You can open multiple instances of Jet Data Manager on the same machine to work on multiple projects simultaneously. All instances use the same settings file, however, if you change the repository in one instance, this will take effect for all open instances. This can have unpredictable consequences, so Jet Data Manager will now show a warning if it detects that the repository has been changed outside that instance.
When you enable the project setting “Use Integration Services (SSIS)”, SSIS folders will now be enabled be default. They will also be enabled as a default on any new environments you create. SSIS folders are very useful since they prevent SSIS packages with identical names from overwriting each other.

Previous versions had a setting for enabling Active Directory (“AD”) integration. When AD integration is enabled it is possible to browse servers on the local AD by clicking the “…” button next to the server name. When creating the new Options window, we found the setting to be superfluous, so in the new release, we have enabled AD integration and removed the setting. Our hope is that more users will find and use the feature this way.


This release deprecates the following features and settings:

  • Time tables. They have been replaced by date tables.
  • On tables in the data warehouse: Data aggregations. Use an aggregated table instead.
  • On staging databases: Data mapping. There are many better ways to do this in newer versions of the Jet Data Manager.
  • On field-to-field data movement operations: Split and concatenate. A custom transformation is a better way to this.
  • On conditional lookup fields: Force sub select, Use temporary table and SQL mode. The new algorithm introduced in this version does not make use of these settings.


Jet Enterprise 2017 (17.1.10)


Overview of the New Features and Improvements in Jet Enterprise 2017

Jet Enterprise 2017 (17.1) introduced a number of important new features and improvements. Below is an introduction to the changes made in this version of Jet Enterprise.


Feature Description KB Article
JDM Simple Mode For situations where you simply need to copy data on a one-to-one basis from your data source to your staging database, Simple Mode is optimized for speed. Jet Data Manager Simple Mode
Improved Data Selection In JDM 17.1, selecting all tables from a data source for including in the staging database is now a one-click operation, and a wizard is now available for selecting table and fields from the data source. Creating a Data Selection Rule
Data Selection Templates Data Selection (xml) templates contain information about the selected tables, fields, primary keys, and incremental load settings you use, and allow you to apply these same settings to additional projects Reuse Data Source Selections
Incremental Load Wizard When you have more than a trivial amount of data in a table, incremental load becomes incredibly useful. While setting up incremental load for a single table is fast and easy in previous versions of the JDM, in this release you can set up incremental load for any number of tables in a wizard-style interface. Configuration of Incremental Loading
Automated Delete Handling for Incremental Load If you use incremental load on a data source, and records are deleted, the tables in your data warehouse can become out of sync with the data source. In Jet Data Manager 17.1, automated delete handling is available as an option on incrementally loaded tables. Configuration of Incremental Loading
Using 'Raw-Only' fields "Raw-Only" fields can now be defined in a staging database to allow you to define fields which may be used for calculations or data cleansing (ie: behind the scenes stuff) but wouldn't need to be displayed to the end users for reporting. Using 'Raw-Only' Fields to Hide Data not Needed for Reporting Purposes
Overriding Data Types

The world of data is growing and new data sources appear every day. These sources can vary wildly but when you consolidate them all in one data warehouse, all data needs to have a data type that conforms to the Microsoft SQL Server.

The JDM now includes a new Data Type Override feature to handle tasks like these.

Synchronization of Data Types in the Data Warehouse
Improved Snippet Management

All snippets are now managed in one consolidated window, from where, you can add, edit, organize, import, and export all snippets regardless of the type. To further streamline the snippets feature business functions have been renamed OLAP snippets.

How to use SQL and Business Function (OLAP) Snippets
Easier Application of Constraint Suggestions

In the new version of the JDM, you can now get primary and foreign key constraint suggestions for all tables in a staging database or data source and apply them all at one time. This functionality uses the new Automate wizard interface that also powers the new incremental load setup feature.

Constraint Suggestions In The Jet Data Manager
Setting Database Schemas at the Data Source Level In previous versions of Jet Data Manager you could define a database schema at the data warehouse level and the table level. In scenarios where the number of tables is very large, schema usage can very useful for keeping tables organized. Jet Data Manager 17.1 allows you to set a schema at the data source level as well. Database Schema
Safer and Faster Hashing Algorithms In Jet Data Manager 17.1, we have overhauled the hashing algorithm to make it easier to debug hashed fields and to address some limitations in the earlier implementation that could cause problems with very large history-enabled rows. Hashing Algorithms in the Jet Data Manager
Setting Data Type Defaults for New Fields The Add Custom Field dialog now includes an option to set your own default settings for a specific data type - allowing you to add multiple fields with settings that deviate from standard defaults Set Data Type Defaults for New Fields In The Jet Data Manager
Remove Highlighting of Object with Descriptions It is now optional for the JDM to display objects with descriptions in bold face. Remove Highlighting of Objects with a Description in the Jet Data Manager
Configuring Security on Tables in the Staging Database. In previous versions of Jet Data Manager security could only be managed on the data warehouse. Because it can very useful, we have added the security setting to the staging database, as well. Configuring Staging Database Security


Jet Data Manager 16.10.4

Minor Fixes / Bug Fixes

  • Dynamic Project Variable resolution error
  • Query table: CommandTimeout is not updated correctly in SSIS package
  • Junk dimension dialog issues
  • Remove unused sections from documentation feature and include external SQL Connections
  • Project perspectives: Program terminated due to missing check if table is of type view or table
  • Possible protected project corruption
  • Resolve issue with Remote Environment Deploy Full with Managed Execution

Jet Data Manager 16.10.3

Minor Fixes / Bug Fixes

  • Cannot deploy and execute OLAP Server with offline processing when having OLAP roles on the database.
  • Conditional lookup can use itself as join when using table relations.
  • Custom table insert: Unable to add unless two tables are present.
  • Execution package: Wrong cast can be made under certain circumstances.
  • Security roles: Unable to deploy role after deleting a fields from a table included in a security role.
  • Table insert: Command timeout not set on BulkCopy.

Jet Data Manager 16.10.1

New Features

  • The new Differential Deployment is a more efficient way of only deploying the parts of your project that are required.
  • The Deployment Status Report is an export file that contains a list of what needs to be deployed.
  • The new Managed Deployment helps to manage dependencies for the user.
  • Now the Data Export allows you to push the content of a data warehouse to another database.
  • The new Dynamic Project Variables is a kind of project variable where the value of the variable is generated by a custom script written by the user.
  • New Custom Table Inserts give the user the ability to write their own table inserts.
  • Users can now Guard Data Sources which prevents tables that get their data from the data source from being deployed, executed or both.
  • You can now show the Data Types on Fields in the project tree.
  • You can now create relations between the system fields added by JDM and other system fields or regular fields.

Improved Features

  • In order to accommodate the new deployment features the Deploy/execute Workflow has been redesigned.
  • New support for SQL and Oracle data sources and the Dynamics NAV and Dynamics AX adapters.
  • Users can now limit access to certain functionality to Active Directory (AD) groups using Environment Security.
  • Column Permissions is an improvement to the object level security feature by adding a new level of granularity.
  • Incremental Cube Load Improvements
  • Faster Setup of History Tables
  • Easier to Choose Tables for Full Load
  • Improved Performance with Batch Data Cleansing allows users to choose to split the INSERT statement up in batches during data cleansing.
  • Better Performance when Full Loading Incremental Tables
  • Related Tables Included in Dynamic Perspectives
  • Execution Package Setup is now Logged

Minor Fixes / Bug Fixes

  • Ftp task: JDM crashing when trying to delete a FTP task
  • Invalid table settings: Empty tables right after execution
  • DateTable: FiscalYear is advanced 1 year ahead of normal year
  • JDM Environment Error dialog spelling mistake
  • Resume Execution Issues
  • Relations added by constraint suggestions is added twice and in wrong location
  • Executing an external business unit error message missing
  • Remote Security Controller Optimization - Added resolve cache
  • Step null reference logging errors
  • Impact analysis on field not showing impact with usage in conditions
  • UI update error when drag-dropping a transformation from one field to another
  • Change to User Rights prompt user several times about save/close
  • Cubes incremental loading issue
  • Wrong Editable Name for Adapter fields in Business Unit
  • Deploy/Execute Completed node color
  • Staging DW_Id cannot be mapped to DWH DW_Id from Data Movement Pane
  • Differential deployment additional NAV datasources
  • Join Condition Treating NVARCHAR as INT
  • Excel data field edit dialog looks strange
  • External business unit and "postfix valid tables" setting error
  • Executing external business unit errors
  • OLAP KPIs can have empty names and names already in use
  • Checkpoints working incorrectly
  • Aggregate Table: Doesn't update datatype if changed due to synchronization
  • Tooltips disappear too soon
  • Wrong display of time in deploy/execute dialog.
  • External business unit with pre/post script managed execution
  • Concatenate table support: Qualifying field names
  • Concatenate table support: Changing field names
  • Missing documentation items
  • External step failures do not pass on original error message
  • Data source name validation
  • JDM makes unnecessary connection to remote environments




Jet Enterprise 2016 Update 1 introduced a number of important new features and improvements around data warehouse functionality and the deployment and/or execution performance. Below is a collection of features added in this version of the Jet Enterprise along with links to the relevant KB articles.

Feature Description KB Article

Differential Deployment

Differential Deployment adds more automation to the deployment process by deploying parts of your project without deploying everything.

The Deployment and Execution Process

Managed Deployment

Managed Deployment adds more automation to the deployment process by managing dependencies to make sure that objects are deployed in the correct order. The Deployment and Execution Process

Deployment Status Report

Deployment Status Report is an export that contains a list of what needs to be deployed. You can generate the report for projects, data warehouses, business units, and OLAP servers. The Deployment and Execution Process
New Deploy and/or Execute Workflow The deploy and/or execution workflow has been redesigned to accommodate the new deployment features. The Deployment and Execution Process
Data Export Data Export allows the user to push the content of a data warehouse to another database. Supported by SQL Server (including Azure SQL), Oracle, and text files.

Data Export

Dynamic Project Variables

Project variables allow the user to save information in project-wide variables for use in custom transformations, scripts actions, custom views, customized code and selection rules.

Dynamic project variables is a project variable where the value of the variable is generated by a custom script written by the user.

How to Use Project Variables and Environment Specific Selection Rules

Custom Table Inserts The ability to create Custom Table Inserts has more flexibility compared to the Table Inserts feature already available in the product.

Custom Table Inserts

Guard a Data Source When guarding a table or data source will NOT be deployed and/or executed when the normal deployment and execution of the project is done.

Guarding a Table in the Jet Data Manager

Environment Security Environment Security allows you to limit access to certain functionality to members of specific Active Directory (AD) groups. The Jet Data Manager will also log events in the environment to the Server Log table in the repository.

Environment Security

Improved Data Warehouse Column Permissions Column permissions allow the user to set permissions on specific columns/fields on a table, not just the entire table. Data Warehouse Security JDM 2016 and Newer
Execution Package Improvements Execution packages now have a managed execution section that will decide the order in which objects are executed based on dependencies.

Creating an Execution Package

Batch Data Cleansing The Jet Data Manager has the ability to split an INSERT statement up in batches during data cleansing. This saves log space on the SQL Server which gives you better performance on large tables with millions of rows. Batch Data Cleansing

Related Tables Included in Dynamic Perspectives

The JDM now takes table relations into consideration when calculating what tables will be included in a dynamic perspective.

Using Project Perspectives in Jet Enterprise

Execution Package Setup is now Logged The new release contains an addition to the execution log. In addition to the execution diagram
and message, you can now view the settings used for the execution.
Execution Logging and Statistics


Jet Data Manager 16.2.3

New Features

  • Support for SQL Server 2016
  • Adding the ability to add Usage Conditions to execution packages for better control over when execution packages run, such as having full load executions only happen in a production environment but not the development environment. ( Creating an Execution Package )
  • Custom password protection has been added for SSIS packages that use SQL Server logins ( Custom Password Protection for SSIS Packages )


Improved Features

  • Improved selection criteria for AX companies that allows new companies to be automatically included when data is pulled ( Add Dynamics AX Adapters )
  • Expanded the functionality and usability of Project Variables allowing developers more flexibility ( How to Use Project Variables and Environment Specific Selection Rules )
  • Improved Project Perspectives by allowing the deployment of a perspective in a remote environment as well as being able to execute perspectives that include cubes. ( Setting Up Multiple Environments: Single Server Configuration )
  • Improved support for subscription licensing by having the JDM automatically contact the activation service when there is less than 30 days left before the expiration date of a license.
  • The performance around the amount of time it takes to open projects has been drastically improved for larger projects with many versions.
  • Significant performance improvements when using conditional lookups on large tables.
  • The maximum size of NAV Option Field lengths has been increased to 4000 characters.
  • Support for additional SQL Server data types such as "time", "datatimeoffset", or "XML".

Minor Fixes / Bug Fixes

  • Wrong Data type in Transformation View in fixed transformations
  • AutoIndex: PK Index on Raw - Issue with BK_Hashkey enabled
  • Better handling of unsupported index types
  • IsDirty not set when editing an Aggregate Table’s DataGridValues
  • Error adding external business unit containing a mapping table
  • External BU: Only possible to drag one table at a time and not the entire tables-node.
  • Edit custom data on empty table
  • Add/Edit Prioritization with External business unit in the project
  • Upgrade project repository with empty backup file location
  • Staging Name not changed when renaming External Table connector
  • Multiple Environments: Crash with unhandled exception on second transfer in same session
  • Markup scripts loads project variables as parameters
  • Not possible to use a View in a Table Insert
  • Unable to extract System Fields from Source
  • Issue with the +1 function on the Add Join dialogue
  • Views missing as parameter in stored procedures
  • Aggregate DataField edit group-by/aggregation type error
  • Deploy table with source based incremental rule with spaces in source name error
  • Incremental load on CRM Online fails if blank space in Data Source name
  • Issue with Incremental load on DWH when blank space in DWH Name
  • Incremental Update of Cubes not working with Distinct Count Measure
  • Perspectives: Wrong execution order
  • Execution Packages: Full load tables not deleted from list if deleted from the project
  • Incr. load on cubes does not update partitions when the fact table has been truncated
  • Fixed DateTable name length errors
  • Date Table Custom Period Column Name error
  • Perspectives: Wrong order and multiple instances of same item
  • Condition on a transformation is not loaded correctly on DWH
  • DistinctCount measure fact tables is processed full every time on incremental loaded cubes


Jet Data Manager 15.12.4 (Bug fix release)

Resolved Issues

  • Fixed issue where users could not open a project when a Custom Condition was being used on a SQL Snippet transformation
  • Fixed issue that would throw an "Error loading project tree" error when a fixed join was being used on a text field with an empty value

Jet Data Manager 15.12.3 (Bug fix release)

Resolved Issues

  • Fixed issue where scheduled executions would fail in some instances with a "Index Out of Range" error.
  • Fixed issue where the AccentGrave and Quote option in ODBC connectors was switched in the code, forcing upgraded projects to fail and preventing new NAV Native connections to be made.

Jet Data Manager 15.12.1 (Bug fix release)

Resolved Issues

  • Fixed linked server issue in External SQL connection
  • Fixed problem with execution packages that use sub packages
  • Resolved problem with Full Load feature in execution package not working with some adapters
  • Resolve Binary incremental problem on GP adapter
  • Resolved problems with project not able to be deployed to SQL 2005

Jet Data Manager 15.11.3 (Bug fix release)

Resolved Issues

  • Fixed problems with custom periods in date table and added Saturday as an option for the start of the week
  • Fixed problem with some varchar and text SQL data types on AX and NAV
  • Resolve issue with some AnySource view schema options missing
  • Fixed issue where Query tables would not apply the schema the first time
  • Resolved issue with usage conditions for data selection rules on adapters
  • Resolved issue where some junk dimension keys could cause project corruption


Jet Data Manager 15.11.1 (Jet Enterprise 2016)

New Features

Improved Features


Overview of New Features and Improvements in Jet Enterprise 2016

Jet Enterprise 2016 introduced a number of important new features and improvements around data warehouse functionality and execution performance. Below is a collection of features added in this version of the Jet Enterprise along with links to the relevant KB articles and videos (when applicable).


Feature Description KB Article Video
Data Warehouse Security Provides administrative control of data warehouse security and automatic creation of roles and secured views from directly within the Jet Data Manager. Data Warehouse Security (JDM 2016 and Newer)
Execution Prioritization Provides execution level control over which objects are processed first, such as copying over all raw data from the data sources before any data cleansing is done to minimize the window of time that the JDM is pulling from a database. How to Use Prioritizations in an Execution Package
Date Table Automation Enhances the existing functionality for generating dynamic date tables by allowing the user to have better control over date formats, names, and using custom periods such as holidays. Using the Date Table
AnySource Adapters Extends integrations into any data source that has an ADO or OLE DB data source provider installed on the machine. This supports connecting to a much wider variety of native and third-party data sources such as Facebook, Twitter, Google Analytics, and many other cloud-based platforms. How to Use an AnySource Adapter in the Jet Data Manager
SQL Database Cleanup Wizard Provides an easy way to clean up the staging database and data warehouse by automatically displaying objects in the database that are no longer used in the project and providing an easy interface for removing them. How to Use the SQL Database Cleanup Wizard
Improved Aggregation Tables Enhances the way that aggregation (summary) tables work to provide a better user experience in addition to improved performance and flexibility. How to Use Aggregation (Summary) Tables in Jet Enterprise
Dynamic Project Perspectives Supports the creation of project perspectives that will automatically include all objects needed to execute a particular module. This allows the user to simply select the Sales cube, for example, and have the Jet Data Manager auto-select all dependent objects, therefore making the creation and maintenance of project perspectives much easier. Using Project Perspectives in Jet Enterprise
Full Loading and Excluding Objects from an Execution Package Execution packages now support fully loading a table that is incrementally loaded as well as excluding specific objects from the execution. This greatly enhances the flexibility provided by execution packages in the project. Creating an Execution Package
Limiting Concurrent Transfers from a Data Source Provides an easy way to limit the number of concurrent transfers from a data source if the data source only supports a certain number of connections. How to Limit Concurrent Transfers on a Data Source No video
Project Variables and Environment Specific Selection Rules An interface has been added that allows variables to be used across multiple objects in a project as well as providing a way to support environment-specific data selection rules such as limiting data used in the development environment to only records for the current year to reduce processing time but automatically loading all data once the project is transferred to the production environment. How to Use Project Variables and Environment Specific Selection Rules No video
Physical Foreign Keys Automatically creates foreign keys in the data warehouse based on relationships that have been defined in the Jet Data Manager. This enables front-end tools such as Jet Essentials and Power BI to automatically detect relationships between tables, therefore making the data modeling process much faster. How to Create Foreign Keys in the Data Warehouse No video
Resuming an Execution Package After Failure Enhances the execution process by allowing a user to restart the execution package where it left off in the event of a failure occurring during the execution process. How to Resume an Execution Package after Failure No video
Partial Deployment in Multiple Environments When using multiple environments (such as development and production) the Jet Data Manager now provides users the ability to only move only necessary objects to the production environment rather than having to move the entire project as was necessary in prior versions. How to Partially Deploy Objects in a Multiple Environment Configuration No video
Allow a Data Source to Fail During Execution Provides users with a way to flag certain data sources as being allowed to fail so that the rest of the execution will continue. This ensures that non-critical data sources (such as an Excel file being moved) will not prevent the entire update process to stop. How to Allow a Data Source to Fail During Execution No video



Jet Data Manager 14.5.13 (Bug fix release)

Resolved Issues

  • Fixed issue with NAV Adapter synchronization
  • Resolved syntax issue with incremental load on NAV Native with mutiple fields in the selection rule
  • Fixed Change Data Source memory exception
  • Resolved ODBC DataType System.TimeSpam problem
  • Resolved issue with IBM DB2 not able to deploy using SSIS
  • Resolved GP Adapter problem with global databases
  • Fixed AX synchronization error when no enums present in the AX database
  • Resolved FTP Source ExecutionNumber error
  • Fixed OLAP security error of "Object not set to an instance of an object" when deploying to the front database using Offline Cube Processing
  • Resolved issue with OLAP setup missing in connection manager
  • Fixed problem with documentation not working when having external tables on a Business Unit



Jet Data Manager 14.5.9 (Bug fix release)

Resolved Issues

  • Issue with duplicated fields on SQL Server data sources
  • Issue with selection rules on External Tables
  • JDM NAV Adapter (NAV 2013 and newer): Changed max length of Option Values
  • JDM NAV Adapter (NAV 2013 and newer): Issue with Option String values when empty
  • Salesforce Adapter: Fixed issue with reading very large numbers

Jet Data Manager 14.5.8 (Bug fix release)

Resolved Issues

  • Salesforce adapter does not load data into raw table for Picklist and Multiple Picklist tables
  • Wrong dialogue shown on "Edit Stored Procedure" and "Edit User Defined Function"
  • Application crash when upgrading a SQL Snippet with parameters
  • Performance issue when opening execution packages that call other packages
  • Problem in T-SQL Query window when a varbinary field contains NULL

Jet Data Manager 14.5.7 (Jet Enterprise 2014 SR2)

New Features


Jet Data Manager 14.2.6

  • Resolved issue with table not being marked as dirty if the order of the transformations has changed
  • Resolved issue with incremental load using TimeStamp fields on SQL Server data sources
  • Resolved issue with upgrade error on tables classified as Large Dimension or Large Fact Table
  • Resolved issue with SQL 2005 unsupported Declare statement in Stored Procedures
  • Resolved issue with execution order on lookup fields not being calculated
  • Resolved issue where order of transformations on multiple environment deployment can be wrong
  • Resolved issue with OLAP Front Database Name too short

Jet Data Manager 14.2.5 (Jet Enterprise 2014 SR1)

Jet Data Manager 14.0.3 (Jet Enterprise 2014)

New Features

Issues Resolved

  • Partition template with Numeric Range Value does not work
  • Hierarchy Table Id field data type
  • Writeback with Parent Child Dimension
  • Problem with Force Unicode on AX Adapter
  • Associated measure group is not saved or loaded on Business Function measures
  • CRM Adapter connection issues
  • Reapply Calculated Measures and Script Commands cannot apply to front database
  • DWH Aggregations not correct when based on incrementally loaded staging table(s)
  • AX Adapter Additional Adapter problem
  • Add DimensionLevel on ParentChild wrong default values
  • NAV Adapter with Source Based Incremental load fails on SQL 2012
  • Error on Save when removing NAV Native additional adapter
  • Deployment of OLAP user rights is slow
  • Selecting text in the Description dialog can fail
  • German SQL Server and incremental on datetime fields
  • AX Adapter cannot synchronize accounts
  • Associated measure group is overwritten when definition is updated
  • GP adapter can fail on load project
  • Bug in IsTombstone code
  • Source Based Incremental timestamp cannot subtract
  • incremental load does not work on GP adapter using alias
  • GP Adapter fails on data load when company field is forced to be nvarchar
  • Pre/post script problem
  • Bug in Referenced Dimensions
  • Bug in Associated Measure group on Calculated Measures
  • Resolves some issues when importing project
  • Bad message when importing a project as latest version
  • Bug: Missing 'Refresh' when building drag-drop dimension with '2 field key'
  • Missing refresh when changing the Role name for a dimension
  • Problem deleting a full data source



What's New in Jet Enterpris 2014

Jet Enterprise 2014 offers a large number of improvements and new features. The link below contains a document that outlines what these features are and how they are used.

Jet Enterprise 2014 Product Enhancements

This list provides an overview of some of the new features added to Jet Enterprise 2014:



Jet Data Manager 12.9.9

New Features

Issues Resolved

  • Fixed issue with HalfYear and QuarterName fields in Date table
  • Fixed issue with an error occurring when deleting a field from a view
  • Fixed issue with hierarchy table not being marked for deployment when modified
  • Fixed issue with Value parameters in calculated measures not being saved
  • Fixed issue with display of elapsed time in execution dialog
  • Fixed issue with staggered fiscal year not working on German SQL Server

Jet Data Manager 12.7.0

New Features

  • Support for System.Timespan when using ADO.NET transfer
  • Ability to copy data from fields in the error/warnings tab grid
  • Ability to see more details about a cube by right-clicking on the cube in the Cubes tab
  • Ability to select the start-from step in an execution package
  • Addition of SSIS logging
  • Support for text file data sources with Fixed Width and Ragged Right Formats
  • Ability for the user to specify the SSIS root folder to be used

Issues Resolved

  • Resolved markup script translation for hierarchy levels
  • Resolved issue where the dimension browser would fail with a "Provider cannot be found" message
  • Resolved issue where the application would crash when setting a Data Aggregation to None
  • Resolved issue when deleting an object that is used in a SQL Snippet
  • Resolved error when synchronizing an External Business Unit
  • Resolved issue when using ADO.NET when there was a field with a money/smallmoney data type
  • Resolved issue where Business Function Scripts were not properly deployed
  • Resolved issue where OLAP Security would not be properly updated on SQL 2012
  • Resolved issue with High Availability Cube Processing in a Development Deployment Toolkit environment
  • Resolved issue where NAV Adapter had for NAV 2.60 had problems with non-Western characters
  • Resolved issue with Source Based Incremental Load on NAV Adapter when company name has Unicode characters
  • Resolved issue where features in trial license do not always get loaded on first activation
  • Resolved issue where some tables are unnecessarily marked as dirty
  • Resolved issue where a markup script parameter name cannot be renamed
  • Resolved issue where multiple "Delete Hierarchy" menu items appear in the hierarchy menu
  • Resolved issue where the Multiple Environment window would close unexpectedly if the user tried to create a database that already exists
  • Resolved issue where command timeout on SQL object creation is always 30 seconds
  • Resolved issue where enabling writeback on cube will fail on deployment
  • Resolved issue where DW_ID is not set to the primary key on tables
  • Resolved issue where there would be an error loading a project when using Dimension Level as a parameter in a calculated measure
  • Resolved issue where Single Table Usage is ignored when using source based incremental loading on the NAV Adapter
  • Resolved issue where project could not be opened with message "Error loading Markup Scripts"
  • Resolved issue where cube browser was not using front database when High Availability Cube Processing was enabled
  • Resolved issue where Edit Custom Field was missing in a Time Table


Was this article helpful?
1 out of 1 found this helpful