Overview of the Latest Features and Improvements in Jet Analytics
Jet Analytics 2020 (version 20.1.7 of the Jet Data Manager) introduces new features and improvements. Below is an introduction to the changes made in this version of Jet Analytics. For a more comprehensive list include Bug Fixes see the Release Notes linked below.
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
Download of 32-bit version of TimeXtender
TimeXtender Client version
Jet Analytics 2020 (20.1.7)
May 8, 2020
Dynamics 365 Business Central Verified
This version of Jet Analytics has been validated and works with Dynamics 365 Business Central Release Wave 1 (BC16).
ImageCache Implemented to Improve Project Load
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.
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.
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.
'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.