Product Updates

Our June 2021 exMon DM 3.1 update mainly contains big improvements to already existing features.Convert database tables to exMonDM tablesUsers can now select tables that exist in the exMon DM Database and convert them to exMonDM tables.Fivetran improvementsIn our last version, we introduced the Fivetran data connectors feature. We have now made some improvements for better usability. Tables will now be converted automatically to exMonDM tables and will be located in the Fivetran project folder. Required ColumnsNew property to table columns indicates whether the column must include a value. This property is set for each column in the Table Designer.If the table does not contain a value in a required column an error icon is displayed indicating that it's missing and a message is shown before saving to ask the user if they want to ignore the errors.Database User ImprovementsDatabase users can now be given permissions to create stored procedures, functions, views and tables across all schemas to the database user has access.Table IndexesSystem columns can now be added to custom exMonDM indexes.Open table in the browserUsers with web enabled can now open their tables in the browser from the desktop application. The 'Open in Browser' button is located in the Advanced tab of the Table Editor.Bugfixes & Minor fixesTable EditorError message gets lost when action fails on save in a table Error when importing data from the 'Import data' button in the toolbar and set ignore to all columns Trying to import into a table with no columns needs to notify users that they need to add columns first Unable to refresh open hierarchy after making changes to attribute namesTable DesignImport from database action saved to toolbar shows icon name as the action name Renaming table does not rename it in the tab Edit connections in import data when the already existing table is open doesn't work Warn users if they are trying to create two new SQL tasks that have the same name. Make the save button disabled. Changing values for multiple columns simultaneously did not always workUser AccessPossible to press next when adding a new user without writing an emailOtherRemoving system keys from API share Sometimes generating a password for a DB user does not automatically pass password enforcement(missing 2 of 4 requirements) Save in settings doesn't disable save and navigation buttons while saving Telemetry crashed program when user could not connect to application insights An exporting project that contains tables with lookup columns would fail when the lookup table itself was not part of exported project

In exMon 5.9 we made improvements both in exMon Data Governance and in our next-gen version, Turnkey.exMon Online supports on-premise process managementexMon Online, the SaaS version of exMon where we offer exMon in the cloud, now supports executing processes On-Premise. That means we can orchestrate hybrid data processes where parts of the tasks are On-Premise and parts are in the cloud while visualizing the processes on a live map.This can be really helpful when migrating your data pipeline to the cloud.Multiple service support in exMon OnlineexMon 5.9 now supports quickly switching between services. This can be really helpful for people with more than one exMon Online instance.ImprovementsTimeXtender installation path can now be changed from the default path. Packages that ran through the Command Service now show up correctly in the Execution History TreeTurnkeyOur next generation of exMon, codenamed Turnkey, is now in private beta and we are constantly improving based on user feedback.Exception OverviewImprovementsUsers can now stop the scheduled execution of datasets Rule filter no longer shows two scrollbars User no longer enters authentication loop when he is lacking access to customer Rules that have been deleted are no longer shown in the recently executed list

Our November 2021 exMon DM 3.2 includes two new types of Actions and improved stability of the web.exMon DG integration actionWe have introduced a new feature that allows you to run actions in exMon DG directly from the exMon DM action panel. So whenever you want to run exMon DG tasks based on your exMon DM data you can do so - by simply adding a new action, choosing your desired task and configuring it to your liking.Read more about exMonDG Integration ActionPowershell ActionThe other new type of action is a Powershell action. You can now create an action that executes a PowerShell command. Within the PowerShell action, table data can be accessed and used.Read more about Powershell ActionBugfixes & Minor fixesTable EditorThe Clear filter doesn't clear the search Values in lookup columns are updated on save when a row is lockedOtherBetter error message when the user can't connect to the database The application looks weird on some laptop screens Improved stability of web Delete category sometimes failed 

We are excited to bring you the exMon 22.3 release with many new features and improvements. Recently, we have been integrating exMon Data Governance and Data Management to ensure they work seamlessly together. With this release, we are taking the next step by synchronising releases and having a common versioning scheme. Therefore we made the jump from exMon DG 5.9 and DM 3.2 to a version that uses the current year.Our goal is to release 4 major versions a year with smaller improvements in between.SummaryThis release brings an update to the data connector - for future references data gateway - this will now allow you to connect to on-premise data and data pipelines from the cloud. Everybody hates too many emails - so now we have added a summary function for email notifications to make it easier to get an overview, get fewer emails and reach inbox zero.Amongst some of the new features we have of course fixed some bugs.exMon Data GovernanceexMon Gateway and Process ManagementexMon Data Connector has been renamed to exMon Gateway for better clarification. exMon Gateway can be set up on any computer within an internal network, allowing cloud customers to connect to on-premise data and data pipelines.exMon Gateway now supports running packages on-premise. This means that our cloud customers can now seamlessly control and monitor on-premise TimeXtender, Jet Analytics, SSIS and custom PowerShell, Python etc. jobs using the cloud version of exMon.A common use scenario could be a customer using on-premise SSIS packages needing to run in parallel with TimeXtender execution packages. When they are finished, exMon is used to ensure the data is correct and finally update the PowerBI reports.Email Summary ImprovementsEmail Summary is a great way to send a weekly digest of the progress for specific data quality controls. With exMon 22.3, we are also improving email summaries sent to query owners. One significant improvement allows you to turn off email for specific data quality controls and instead send out a summary.exMon Data ManagementOpen exMon DM Application from the webIn each release, we have been improving the experience in using the overall data entry user experience in the exMon DM web portal.In exMon 22.3, we have added a new toolbar button, Open exMon DM App. This button allows the user to open the current table in the Windows client version of exMon DM. This allows the user to quickly jump into the Table Designer to make changes to the design.Improvements on the webFurther exMon DM web client improvements include better functionality when scrolling and filtering through large tables and filtering. The filter panel is now located next to the data instead of on top of it so all columns are visible. Upgrade Later between Minor VersionsOur aim is to keep all clients up-to-date on new features and improved stability. Therefore, we frequently release new versions of exMon. When we publish new versions, users are given the choice to upgrade their Desktop Client immediately or later on.exMon TurnkeyOur next generation of exMon, codenamed Turnkey, continues to be in private beta. It is continuously being improved based on user feedback.Process MapsTo get a better overview of the processes running in the workspace, we have added a process map that allows you to monitor a variety of processes.(Image: Process map)(Image: Failed process in the process map)Adding usersWe’ve added the beginnings of user management into turnkey, starting with creating a new user.Data providers addedWe’ve added a data provider page to turnkey to add and/or manage data providers.(Image: Data providers page)(Image: Data provider creation)Bugfixes & Minor fixesThe execution preview has been improved The preview dataset no longer shows two scrollbars Improved error messages in execution preview Compare queries now work in TurnkeyWe are slowly adding new beta testers to Turnkey and we are excited to bring this to more users in the coming months.Bug fixes and smaller improvementsData GovernanceAzure Function as a new package type Upgraded all code to .NET 6, improving speed and size exMon cloud now uses SendGrid for emails, improving reliability Null exception is thrown when the task is deleted Data connector should not need to be upgraded to work for newer versions of DG TimeXtender packages throw a wrong error message Users cannot change portal colours under Tools -> Configuration Description and Action for Email Template do not work Create data provider - UI is disabled after selecting PowerShell as datasource type Fix error where test execution fails because too many tests are running through the command service Better error message when the user has not executed test in query window before previewing/executing it fully Command service is now 64-bit by default Disabled tasks throw an exception Dashboards in old DG don't work CommandService is not included in the on-premise installer Upgrading exMonDG on-premise does not work correctly for the CMD service Recalculate hashes sometimes fails Switching to Dimension overview does not work  After deleting the system in old DG, tasks that were on the system can still be executed When logging in on the DataFactory package that has values on the initial load it throws an errorData ManagementSome legacy tables did not work in the web application Upgraded all code to .NET 6, improving speed and size Users could not change the values of Item List in Table Designer Making hidden columns visible didn't work in the web application Users can now copy the full database name of a table from the Table Properties window High-DPI and layout problems in the Desktop client were fixed Column caption in tables automatically added spaces before capital letters When string columns were marked as Summary the table showed now rows More descriptive error message when users delete a column being used by an ActionHow to upgrade?Contact support@exmon.com to upgrade

We are excited to bring you the exMon 22.5 release with many new features and improvements.SummaryThis release brings Single Sign-On (SSO) Login for all exMon products. This allows you to easily log into various exMon products without having to remember multiple different passwords. We have also added new icons to exMon Process Maps; including commonly used company logos and Azure icons.As well as adding new features, we have of course also fixed some bugs.exMon Data GovernanceSSO LoginexMon Data Governance now supports Single Sign-On using Azure Active Directory (AAD). This makes it easier for users to use login credentials, on their local machine, to log into exMon services. Furthermore, this ensures that users who are no longer enabled on your network immediately lose access to exMon. With this release, all of exMon now supports Single Sign-On.For more information on how to enable Single Sign-On visit Single Sign-On Azure AD.New Icons in Process MapsUsers can now choose predefined icons both from a collection of 450 Azure icons, and 19 company logos to insert into their process map backgrounds. exMon Data ManagementImport text file with fixed widthUsers can now import text files with fixed-width columns into existing tables. Read more about this here.Saved views also save single row editUsers can now save a view with a single-row edit view. A single-row edit will appear in the same place as it was saved when selecting a view with a single-row edit view.  exMon TurnkeyOur next generation of exMon, codenamed Turnkey, continues to be in private beta. It is continuously being improved based on user feedback.Activity for issue detailUsers can now access a new section in the issue details which is the Issue Activity. The section lists the history of actions on the issue details, along with buttons for changing the status of the issue.SettingsUsers can now configure their exMon Data Governance service using the settings within Turnkey. The settings allow users to change general settings, email settings, test settings and advanced settings. In order to get to the settings page – you can find a cog icon in the top navigation bar. DM Data ProviderUsers can now create data providers specifically designed to get data from an active exMon Data Management service. This feature allows users to more easily set up data providers, without providing all the nitty-gritty details when setting up a regular database connection string.Create a support ticket when an error occurs in the systemUsers can now report errors that occur in exMon DG Desktop and Turnkey. Each time users encounter an error, they will be given an option to report the error – which will result in a support ticket being created. This will hasten the process of solving the issue for the user that is experiencing these errors. Autosave for datasetsUsers no longer need to worry about saving their datasets when working on them, because they are automatically saved for them. The dataset is saved as a draft, so it will not interfere with the published version of the dataset until it has been published again. Publishing a dataset is still a manual task – because it may have more impact on rules which depend on the dataset. Bug fixes and smaller improvementsData GovernanceUser groups could not be saved Users could not assign exceptions to different user Users with administrator privileges could not log in as a different user User set as Process Administrator could not run tasks on process map Recent Images in Process Map were empty Query Email now shows only a description Exception Email Preview shows Action twice Web did not show PowerShell packages on process maps Running Command Line Package returned "Specified cast is not valid" error Package parameters were not usable by all package types Data Transfer UX improvements Data Provider with system selected didn't show Execution connection with the system all selected TimeXtender data provider UX improvements in Gateway A process that finished successfully eventually sent a timeout email when running in the cloudData ManagementThe import data button did not work in the web application The user experience for Import from the database was improved Tables were not shown when searching for projects in the navigation in the web application The refresh button in the Import Data form didn't work Locking and unlocking rows did not work in the web application Clear filters didn't work correctly in the web application Import in the web application did not support text files Deleting a column that was being used by an index threw an error instead of informing the user of it. Column names in indexes form were empty Users could not edit connections when editing and Import from database action Import action displayed the wrong name in the toolbar Filters were reset when the filter panel was collapsed Users could not add a new project when right-clicking an empty space in the navigationTurnkeyThe workspace key URL was cut off when the screen was too small Setting column as the primary key did not work User status doesn't update in the UI after enabling/disabling a userHow to upgrade?Contact support@exmon.com to upgrade 

We are excited to bring you the exMon 22.6 release with new features and improvements. Summary This release brings an improved PowerShell experience for cloud users in exMon Data Governance as well as a change in behaviour for how items are set to run through execution connection. In exMon Data Management we have been working on feature parity in desktop and web applications.In this release, we introduce the first preview of Hierarchies on the web and the possibility to import fixed values when importing into a table in the web application. We have also added a feature for administrators to give their users access to specific columns.exMon Data Management Hierarchies on the web (Preview) The first preview of hierarchies in the web application is now available. Creating hierarchies is still only possible in the desktop client. However viewing, editing, and managing hierarchies is now possible on the web client.  Read more about the web hierarchies preview here.User permissions for columnsAdministrators can now grant users Viewer or Contributor privileges to specific columns, giving them better control over who can view and edit data. Read more about this here. Import fixed value in web application Previously users could only import fixed values in the Desktop client, but we have now added the possibility to do so through the web application.  exMon Data Governance Running PowerShell in Cloud Cloud users can now run PowerShell scripts in packages and queries without using an execution connection. The script can only include commands that the exMon team has approved. Read more about PowerShell in the cloud here.Execution connection queue Execution connections are used to execute tasks on different servers than the main exMon DG server. With this change exMon no longer requires direct access to the server that should run the task but instead the execution connection polls exMon DG for tasks to execute. This change prevents issues such as execution connection overload and firewall problems. Bug fixes and smaller improvements Data Governance ETA for the process map did not work   Process timed out after it had finished executing   TimeXtender did not allow for custom paths  Links to support pages were updated   Email summary was by default set to true for compare queries   Create table did not work in Data Transfer when the source was set to PowerShell   Passwords containing hashtags did not work in the DG desktop client   Package parameters are now usable by all package types Data Management Create table from imported .csv files did not work   Link to support article “Unable to connect to database” was wrong   Logo in trial popup was tiny An error message after changing privileges for database users    Weird button in the settings form    Fivetran connector with space in schema did not work    Actions set to run automatically after saving did not run after importing in the web client  Saving changes in the execution tab in Actions did not work  Better error message when converting column datatype fails  Changing Import from Database action did not work Turnkey We’ve been working hard on making Turnkey production ready and continue to improve the user experience in many areas. For example, user management, auto-saving, and rule configuration. Furthermore, we have made small fixes where necessary and continue to add new features. The goal is to bring in more beta testers in January. If you are interested, please contact us at support@exmon.com.How to upgrade? In Exmon Data Management, users in versions 22.5 and above can complete the upgrade themselves through the Desktop client. See the Guide.Contact support@exmon.com to upgrade

We are excited to bring you the Exmon 23.1 release with new features and improvements. Summary We are excited to bring you the first version of 2023. In this release, we bring improved hierarchies with added features in the DM web application. In Exmon DG, users can now select default email templates globally, per system, and, per query.Exmon Data Management Hierarchies in web We have continued to work on the hierarchies in the web application. New features that are included in this second version of the preview are: adding children to nodes, unassigning nodes, and improving the experience when moving nodes. Additionally, we have made some smaller improvements and bug fixes. Read more about the web hierarchies this article.Execution queue change for DM’s DG action The Execution Queue has been added to on premise DG actions. With this change on premise Exmon users no longer require direct access to the server that should run the task but instead the execution connection polls Exmon DG for tasks to execute. This change prevents issues such as execution connection overload and firewall problems. Read more about DG actions here.Exmon Data Governance Set email template as default template The ability to set an email template as default for the entire environment or per system has been added to DG. At the report level, if no template is specifically chosen for the report the system level default will be used. If no system level default is set the global default will be used instead. At the system and report level, the current default will be indicated in the dropdown list of templates. Switch from DG portal to other products If your account is associated with multiple Exmon services. You can now switch between them from the DG portal by clicking the service name in the top right corner. Bug fixes and smaller improvements Data Governance Command line packages could not be opened from Execution History Status page on DG portal cloud could not be opened  Error when selecting Data Provider in Source in Data transfer package  Saved Comparative did not always work correctly  Compare queries using DateTime column as value did not work  TX packages ended unsuccessfully when TX had multiple projects DM Data provider does not show up in Data provider command packages  UI for Data Provider type Data Management is incorrect  Incorrect data was shown in Available Data Providers column when creating Data Provider Group  Data Providers were sometimes visible in incorrect Systems  Data Provider Groups are displayed twice in the navigation Sometimes queries could not be opened  Switching from PROD to Development did not work in the web client for cloud users  Some users could not create new queries  Some tasks failed when being run in a Schedule  Cache did not refresh when a user created a new system It was not possible to save Power BI Refresh package without a subscription  Power BI Refresh package did not work correctly Data Management Desktop:  Import into double column did not work  Run Task button disabled when DG Action was opened in the Table Designer  Web application:  Could not open hierarchies with decimal columns  Default values did not work when adding a row to a table  Users without table administrator privileges were not able to change column order in hierarchies  Previously assigned nodes were shown at the top of the Hierarchy instead of in the Unassigned section in hierarchies  Clicking the Exmon logo to go to the start page in hierarchies did not work  The color of read-only columns in tables was wrong  When a child node was added in a hierarchy, the parent node was collapsed, and it looked like the child node had not been added  It was not possible to search for hierarchies in the navigation  The UI was stuck loading after user clicked “continue without saving” when importing into a table in the web application  Running DG Action did not always work  Turnkey In this version of Turnkey, we have emphasized improving the user interface and user experience.  If you are interested in becoming a beta tester for Turnkey, please contact us at support@exmon.com. New UI for Dataset Column SettingsNew UI for Rule Column SettingsHow to upgrade? In Exmon Data Management, users in versions 22.5 and above can complete the upgrade themselves through the Desktop client. See the Guide.Contact support@exmon.com to upgrade

We are excited to bring you the Exmon 23.2 release with new features and improvements. Summary In this release, we have been working on improved integration with Azure and have added Azure Connection as a data provider and Azure Synapse as a package type. We have also continued working on Hierarchies in the web for Exmon Data Management and have added the Delete nodes feature along with other smaller fixes and improvements. Rebranding In both Exmon Data Governance and Exmon Data Management we have updated our logos and colors. You can now see the new logo when you use our products. Exmon Data Governance Azure Connection as a Data Provider We have added an Azure connection as a data provider. Currently, only Azure Synapse packages are using this type of data provider but in the future, it will be connected to other items using Azure connection. Azure Synapse Package added to Exmon Data Governance The option to connect to and run Azure Synapse packages from Exmon Data Governance has been added. In order to use this option the user must first create a Data Provider for Synapse containing the authentication information for the relevant Azure subscription. Once this is done, a DG package connecting to and running a specific pipeline from an Azure Synapse package can be created. Read more about Azure Synapse packages in Exmon here.TimeXtender ODX Package type (BETA) We have added a new Data Provider Type, TimeXtender SAAS, and a new package type that allows you to connect to TimeXtender ODX and execute jobs.  This is a part of our TimeXtender integration improvements to make TimeXtender and Exmon work better together.Exmon Data Management Hierarchies in web We continue working to improve hierarchies in the Exmon web application. We have implemented the Delete branches feature and made some smaller improvements and bug fixes. Read more about the web hierarchies here.Bug fixes and smaller improvements Data Governance Could not create Data Transfer Package with a PowerShell data provider through an execution connection  Users were unable to search for a Data Provider Datasource Type  When a package was run through gateway, it did not send an email to the user  Not all Data Providers were shown when a Data Provider Group was created  A newly created Data Management Data Provider was shown as empty when opened again  User could not run the Data Provider Command package through Gateway  Reports in object groups were not displayed in Process Maps  Failure emails from executions through Gateway did not include error text  The Run button in a Process Map in the Portal did not work properly  Process maps were not ordered in alphabetical order  The User got an error dialog when they opened Test Details in the Portal  Test and Production environment did not work for Test Connection in Gateway Gateway did not use package timeout when it was specifically set  PowerShell command with Select-Object could not be run Data Provider Package did not work through Gateway on PROD  No logging while waiting for a Gateway package to finish  Exception is thrown when the user double clicks background in a Process Map  SQL timeout for Dimensions was too short Data Management ID column was called exTables Row Id instead of Exmon Row Id in Lookup Column Options  Adding a comma to Default Value for Double column was not possible  Create a table with Import from database multiplied decimal and double columns  Help in importing a text file with Fixed Width navigated the user to an error page  The next button was disabled after changing Delimiter from Fixed Width to something else  Users could not move data nodes from a Hierarchy to Unassigned in the web application  Moving root to its branch is possible in a Hierarchy in the web application  Importing a DateTime value with a specific format did not work properly  Lookup to DateTime column did not show the value with the correct format  Read-only columns were not visible to use as a Unique Key column when importing  When user created a Hierarchy with Max Height less than 6 an error was thrown  Deleting a table with a hierarchy did not delete the hierarchy tables and views in the database  Executing DG action did not work  Text overlap between columns in an open table in web application  Client became unresponsive when user tried to remove a Thousand Separator for Large Number column  If an Audit Schema did not exist and the user tried saving a table with Full Audit History On, they got an error and the toolbar stayed disabled. Turnkey We have been working on updating the design and user interface for Turnkey in this release using the new colors for Exmon. How to upgrade? In Exmon Data Management, users in versions 22.5 and above can complete the upgrade themselves through the Desktop client. See the Guide.Contact support@exmon.com to upgrade

We are excited to bring you the Exmon 23.3 release with new features and improvements. Summary In this release, we have added several new features. These include exception tagging in the portal to Exmon Data Governance, a Jet Analytics data provider and package type, test groups. We have also moved the TimeXtender ODX package type from Beta to Stable along with other smaller fixes and improvements. In Exmon Data Management, we have added the Geography data type and support for a larger range of DateTime values. Rebranding In this release, we've given our emails and login page a fresh look by switching from the old logo to the new Exmon logo. We believe this update brings a more modern and cohesive feel to our platform, aligning with our vision for the future. Exmon Data Management Geography Data Type We are introducing a new data type that will bring support for Spatial Location data of type Geography. This means that now you can map points based on the geographical location anywhere on Earth. In addition, Exmon DM will now be able to read SpatialLocation data in databases. To use this type of data, you can either create a new table or a column in existing tables with data type “Geography”.  Support for a larger range DateTime values In some cases, users need to be able to store a larger range of DateTime values than the default DateTime SQL data type. In this case, we have added the option for columns to support this and save the values as datetime2 values instead. To activate this support, check the Support Larger Range box for the DateTime column in the Table Designer. Exmon Data Governance Jet Analytics Data Provider and package typeWe have added an option to connect to and run Jet Analytics packages from Exmon Data Governance. The functionality and usage of the new Jet Analytics packages is identical to the tried and tested TimeXtender packages that have been part of Exmon Data Governance for a while.Tagging on Exceptions in the Portal Users can now create their own tags in the portal. The user can select an exception and select the button Tags opening a modal popup. In the popup, the user can create a tag by writing it in the input and add or remove a tag from the exception which will help users organise their exceptions.The tags will show up in a column labeled Tags and the user can filter the grid showing only exceptions with specific tags.The user can also navigate into exception details and see the tags connected to the exception. They can also see the action history when and what tags were added or removed from the exception.You can read more about Tagging Exceptions in DG Portal hereTest Groups Test Groups allow users to add and configure multiple tests on a specific table in one editor. In this release, there will be three test types available for Test Groups:Null check Empty table Custom SQL.These Test Groups can be created on SQL, Exmon Data Management and TimeXtender Data Providers.  You can read more about Test Groups hereBug fixes and smaller improvements Data Governance All items in dropdown list in Execution Connection field in Data Provider were doubled  User didn’t get email summary after successful execution when creating a new email summary  Data providers were not filtered per system in the Object Browser  Deploy window only deployed tasks it could see  Creating table in DG Data Transfer didn’t work for DM Data Provider Changed logos in DG  Email summary didn't always send an email to user  When user selected an invalid data provider or invalid client secret, all data related to azure package were populated and there was no warning that data provider was invalid  User got an error message when trying to save a synapse package with invalid Data Provider, invalid app ID, invalid tenant Id or empty data connection  Some Data Providers were duplicated in the Data Provider Drop Down field. Error was shown instead of a warning message when no Data Provider/Execution Job was selected  Incorrect icon in Synapse Package  Synapse package always ran successfully with an invalid execution connection  Successful Process failed and Execution History did not show all data  The Execution History button did not work in Email Summaries Dates in Exceptions Details in the DG portal were in Icelandic  The assigned username was not shown in Exception details  Inconsistency in error messages when saving empty packages   TX Saas package failed to run but didn’t write out any error messages  Incorrect icon in Azure Synapse package Buttons became invisible when hovering over them in the DG Portal  Incorrect package name in the header in the Status page in DG web  Error email for packages was not always sent  Dates were in Icelandic in Email to Query Owner  Could not open Exmon DM Data Providers No information in output that an email was sent to CC  Incorrect Azure package icon in Schedule group, Object group and Process  Email Summary was sent to CC users, when send to query owner, was selected Data Management Clicking tab in cells in web made the percentage column 0% instead of null  Table and column viewer didn’t have copy in context menu   No data was in preview when creating a new table when importing from a flat file  Filter in Desktop did not refresh after deselecting  Importing percentage into float column  Files are not deleted from Lib folder when upgrading Exmon applications  Changing the name on SQL Action threw an error  Changed logos in DM  Default value overrode unput value  Hierarchy with max height as 1 threw an error while saving  Error messages were not clear when entering incorrect value  Saving a new branch in Hierarchy threw an error  Remove Edit Hierarchy from context menu in Hierarchy  Copy table was changed to a dropdown button  Import removed space from column name and the user couldn’t find it in web  Issues with inserting values in large number column  DM API large number column treated like a decimal  Error when a user was removed  Excel icon was missing in Export table  Custom settings in import made Import button not visible in web  Updated branding in import email in DM web  Log off URL did not work in DM web  Share table data URL needed a Json format  DateTime dropdown was hidden in import in web  Read Only bool column in web tried to insert null value instead of false  Using Exmon DM table to import into a new table threw error because of system columns  User couldn’t filter the dropdown  Inconsistency in showing filtered data in DM desktop and web  Link to a table with null filter didn’t work Changing the column to a lookup column after importing showed the column as empty on web TurnkeyExplainer: Our next generation of Exmon, codenamed "Turnkey," is our Cloud-first solution that has been modernized and improved for a better user experience. The main objective of "Turnkey" is to provide a low-code solution that is efficient and suitable for both advanced and less advanced users."Turnkey" is currently in private beta mode. If you are interested in trying it out, please contact support@exmon.com. We are continuously working on enhancing it based on user feedback and anticipate its official release soon. Be the first to know by signing up here. We have been working on updating the design and user interface for Turnkey in this release using the new colours, matching Exmon's recent rebranding.How to upgrade? In Exmon Data Management, users in versions 22.5 and above can complete the upgrade themselves through the Desktop client. See the Guide.Contact support@exmon.com to upgrade

We are excited to bring you the Exmon 23.4 release with new features and improvements.SummaryIn this release, we have added several new features including SSO user groups, column dimension validation test groups, Excel file attachment to exception emails and the ability to execute Azure PowerShell packages in Exmon Data Governance.Exmon Data ManagementSSO User GroupsThe introduction of the User Groups feature simplifies the process of assigning privileges to multiple users and logins based on their membership in Active Directory groups. There two types of groups that can be created:Active Directory (Entra ID) based – members are defined by groups membership in AAD Manual – group membership is based on DM´s database and manually assigned by the administrator for that customerThe User list UI has been enhanced to provide a comprehensive view of users and their group memberships with a new column displaying each user's manual group memberships.You can read more about User Groups in DM hereExmon Data GovernanceColumn Dimension Validation in Test GroupsA new test type called Column Dimension Validation is now available for Test Groups. This exciting addition allows you to compare the values in your source data with another dataset, ensuring its accuracy. Dimensions serve as the external dataset for the comparison, providing a reliable and efficient way to validate your data.You can read more about Test Groups hereExcel file attached to exception emailException emails now include an attached Excel file, providing easy access and analysis of the data included in these emails.DG package for AZ PowerShell command packageNow you can create and run packages using Azure PowerShell scripts. Utilize the Azure Connection Data Provider to securely authenticate and connect to your Azure environment as well as define unique parameters and call them as variables in your script. Read more about this here.SSO User GroupsJust like the new feature in DM, Admins can now easily manage privileges for many users at once using groups. Admins create a group by selecting an Azure Active Directory (Entra ID) group or manually specifying a list of DG users. Access rights can then be managed for all members of that group at once, making this process significantly more efficient for admins. Read more about User Groups in DG hereTurnkeyExplainer: Our next generation of Exmon, codenamed "Turnkey," is our Cloud-first solution that has been modernized and improved for a better user experience. The main objective of "Turnkey" is to provide a low-code solution that is efficient and suitable for both advanced and less advanced users.If you are interested in trying it out, please contact support@exmon.com. We are continuously working on enhancing it based on user feedback and anticipate its official release soon. Be the first to know by signing up here.Process Maps Now Viewable in TurnkeyProcess Maps can now be viewed within Turnkey with a refreshed, modern interface accessible to a broader audience. While creating and editing process maps is still done in the DG desktop client, users can now enjoy the ability to execute processes or tasks, access detailed execution history, and view task-specific details and exceptions directly from Turnkey. Please note: Currently, Turnkey supports viewing process maps in the 'PROD' environment only.Enhanced Access to ExceptionsWhether exceptions originate from rules or queries in DG Desktop, Exmon Portal, or Turnkey, you can now view and update the exception status from a single unified interface within Turnkey. This streamlined users experience marks a step forward in our commitment to providing a cohesive and user-friendly environment in Turnkey, with future plans to broaden exception visibility beyond queries for comprehensive data governance support.Please note: Currently, Turnkey supports viewing exceptions exclusively in the 'PROD' environment only.Bug fixes and smaller improvementsData GovernanceError message displayed admin name rather than user email when logging-in to Exmon DG Desktop Data Providers created in Gateway had incorrect Datasource Type in DG Desktop Exmon DG Desktop would not open in 23.2 Exmon DG Desktop would not open in 23.3 User with insufficient privileges to use Exmon DG Desktop could log in but not use it or log out again A check was missing if primary key was unique in test groups Manual run of valid Jet Analytics packages would fail Error description was missing when execution connection was invalid in packages Email summary was not shown on process map in DG Portal Process execution showed incorrect info when task failed Running test groups in DG Portal did not work Email summary did not send correctly to CC users when there were multiple CC users Changed branding from exMon to Exmon in emails from DG Desktop Changed "Start" button to "Refresh" and default value of UAT from "DEV" to "PROD" in DG Desktop Data Provider parameters did not work with Gateway Data Providers User could not log into Exmon with password containing special characters Executing a large number of tests through WCF service timed out Data Provider groups never showed anything as selected Replaced old icons with the new branding Buttons were hidden in Column Formatting in Test Placement of Report button on Exmon error dialog was incorrect Could not create a Test Group Exmon-DM test from template Process map was not updated on PROD Running test groups in DG WEB from process map did not work properly Allowed package parameters for Data Provider Command packages Exmon DG installer would sometimes fail to upgrade Some customers created before 23.3 had a mix of old and new color scheme Could not save Gateway created Data Provider Default "PROD" in preview did not run as "PROD" but "DEV" Global parameters did not work with command line through gateway Compare Queries created exceptions when it should not Data Transfer with Data Management data provider as source would not openData ManagementAuthorize in Fivetran did not work Switch service window would frequently kill the DM program Replaced old icons with the new branding User could not log into Exmon with password containing special characters Improved user interface on front page Toolbar items were not centered Toolbar would collapse even though there was enough space When the toolbar was collapsed the grid would not fill out the empty space Navigation bar was in the wrong color Save button in gridview and nav expand button in header were in the wrong color Improved user interface for copy database command Copy SELECT statement would not copy display columns Logo in DM Desktop and DM Web made more visible Improved error output when DM table failed to load in Web Copy button for SQL statement did not work Last login was shown as N/A for users that had only logged into WebHow to upgrade?In Exmon Data Management, users in versions 22.5 and above can complete the upgrade themselves through the Desktop client. See the Guide.Contact support@exmon.com to upgrade from Exmon 22.4 or below.

It's officially spring in the northern hemisphere and incidentally, we have a bouquet of features and improvements ready for you in TimeXtender 6590.1.NewODX on OneLake: We are excited to introduce Microsoft Fabric OneLake as ODX storage on our platform. This enhancement enables users to seamlessly harness OneLake for all ODX operations, from initial setup and configuration in the Portal to comprehensive integration within TimeXtender workflows. This is the first of many planned integrations with Microsoft Fabric, so stay tuned! Note, however, that you currently cannot use OneLake as your ODX storage if you use Snowflake as your data warehouse storage.  New data source provider for OneLake: A new data source provider for seamless and efficient ingestion of delta parquet tables from Microsoft Fabric OneLake, directly into your preferred storage solution via the TimeXtender ODX. Optimized for ingesting data from OneLake, this feature is not intended for use with Fabric OneLake ODX storage. Publish data as a REST API endpoint: Added a new semantic endpoint, REST API, that works together with a server component installed on-premises or on a virtual machine in the cloud to publish data through REST API endpoints. As getting data through a REST API is a very common use case, the new endpoint type opens up a host of opportunities for integrating TimeXtender with other tools. In our previous major release, 6505, we introduced a new REST data source provider. This means that you can now publish and ingest data from your TimeXtender solution through a REST API using first-party components. New and improved data source providers for Hubspot and Exact Online: The new providers dramatically improve upon the previous CData options with enhanced usability and performance. These new options allow you to easily add custom endpoints and flatten complex tables. To upgrade to the new connectors today just search for the "TimeXtender Hubspot" or "TimeXtender Exact" when adding a new data source connection. Then, in ODX, you can edit an existing data source configuration and change to the new TimeXtender data source connection. Read more about editing data sources. ImprovedYou can now have multiple data warehouse instances open at the same time in Desktop. We've reshuffled the shortcut menu on Data Sources in ODX instances. "Add Data Source" now redirects to the 'Add data source connection' page in the Portal, while the previous "Add Data Source" functionality is now "Map Existing Connection". The intention is to make it clearer that adding a brand new data source happens in the Portal, while "adding" a data source in Desktop is using one of the data source connections mapped to the instance in the Portal.  We've upgraded a lot of our underlying UI framework. You might notice a few changes and improvements to the Portal UI as a result of that. When adding firewall rules to instances, your own IP is now automatically suggestedFixed (Portal)Fixed an issue where data source connection categories would not be shown if the category was assigned a null value  Fixed an issue where MDW/SSL transfers could lead to errors Cloning TimeXtender REST data sources could lead to incorrect data on password fields ODX connection timeout value did not get set correctly Changes to users would not get propagated to identity provider Inputs did not get correctly disabled on SSL Qlik endpoint form Disabled fields would show up as required on the ODX form Fixed issue where the SSL form would sometimes incorrectly flag inputs as invalid, thereby making it impossible to save Fixed incorrect short name suggestion on data source mappingFixed (Desktop)Default settings for key stores were not remembered in the key generation menu for data warehouse instances using SQL Synapse or Snowflake. The parameter '%Instance%' was not working for email notifications. The CSV endpoint was not escaping the text qualifier. On-demand execution from ODX to data warehouse would fail when having the same ODX table in a data area multiple times while using ADF to transfer from an ODX ADLS2 storage. ODX to data warehouse transfer would fail when using ADF and having the same table mapped multiple times, but using different columns in each table. When using a custom field as parameter in a custom measure or calculation group item in a semantic model, the parameter would disappear after closing and opening the semantic model instance and editing the custom measure or calculation group item. Cleaning up mapped objects between an ODX and data warehouse would never clean up the instance mapping causing copy instance in the Portal to always request a remapping of an instance even though it was no longer used. Fixed issue in the semantic model repository upgrade scripts where calculation group and custom script tables were not marked as tables to be included in instance copying  Fixed an issue where jobs completed with errors or warnings were incorrectly displayed as "Completed". They are now accurately labeled as "Completed With Errors or Warnings.   Custom Data on a data warehouse table did not rename the custom data column when the corresponding field was renamed. The data warehouse field validation type 'Is Empty' would mark empty string values as invalid. Fixed an issue where raw-only fields were included in the Data Movement pane. Fixed an issue where preview in Filter Rows in the ODX would always select the first table. Fixed issue where incremental transfer from a ADLS2 ODX with 'Limit memory use' setting failed for empty tables. Fixed issue where transfers from ADLS2 ODX to SQL Synapse would fail if the source table contained reserved system field names.

Today, we’ve published a minor release of TimeXtender ODX Server (v. 6563.1) that contains the changes listed below.FixedFixed a performance issue when transferring data from the ODX to MDW with ADO.NET. The initialization of the transfer of each table mapping had increased by up to 5 seconds for small transfers.

Today, we’ve published a minor release of TimeXtender Portal with the following changes:FixedFixed an issue where copying an instance in the portal would sometimes time out.

Today, we’ve published a minor release of TimeXtender Portal with the following changes:FixedFixed an issue where "Copy Instance" could have the same instance mapping multiple times. This would block the copy instance as a destination instance can only be used once in the instance mapping setup Fixed an issue where "Copy Instance" would ignore some of the table in the SSL instances related to custom scripts and calculation groups when using an SSL instance created prior to client version 6505.1

Hotfix release of TimeXtender Desktop (6536.1) that contains the changes listed below.Fixed Fixed an issue with executing tables in the MDW when incremental load was disabled. 

Today, we’ve published a minor release of TimeXtender Desktop (6534.1) that contains the changes listed below.FixedResolved issue: Truncation of valid table and data override during initial execution after migrating a data warehouse table with Incremental load set to true.

We’ve published a new release of TimeXtender Portal with the following changes:NewNew organization type: Subscription. The new pricing is now reflected in the Portal by the inclusion of a new organization type, subscription, and the four subscription packages. New organization type: Sandbox. Another addition coming from the new pricing is the new sandbox organization type. It allows TimeXtender and partners to provide a sandbox environment for customers on the Premium and Enterprise subscriptions where this is included. Sandbox organizations have a time limit, similar to trials, and can only add one of each instance. TimeXtender ❤ Exmon: You can now unlock and access the Exmon features right from the Home page of the Portal. ChangedIt is no longer possible to add Free or Premium customers. "Premium" has been renamed "Legacy Premium" The search bar on tables is now disabled when loading We’ve added a search bar to the Users list under Admin > Users We’ve added a sidebar to the TimeXtender REST data source connection form.FixedLong data source names were not fully visible in the transfer instance modal Edit preferred support would sometimes fail with an unhandled exception Fixed values appearing twice under data source connection details "Move" user on a Premium customer would throw a "customer manager permission required" The tooltip on the environment description was clickable despite being empty Fixed tooltip placement for missing mapping in environments Fixed spacing on the TimeXtender REST data source connection form Instance names are now truncated if they are too long in the transfer instance modal Fixed an issue where mapping a data source connection would result in an error Fixed an issue in the add/edit semantic model instance form where certain fields in the CSV endpoint wouldn't be correctly disabled The user/customers tables are now refreshed when a new user or customer is added Fixed an issue where the environments page would return an error if no instance had been created Creating a static firewall rule now also creates a connection that can be reused

Today, we’ve published a minor release of TimeXtender Desktop (6521.1) that contains the changes listed below. FixedFixed a race condition issue where the application services could potentially create new connections to the repositories on each repository action, causing the repository to be filled with firewall rules when "automatic firewall rules" is enabled.

Today, we’ve published a minor release of TimeXtender Desktop (6512.1) that contains the changes listed below.FixedRenaming a table in the SSL would cause measures to stop working for the Tabular endpoint. The measures affected were all types except measures using custom scripts or Row Count.

We’ve published a minor release of TimeXtender Desktop (v. 6506.1) and TimeXtender ODX Server (v. 6506.1) that contain the following changes:FixedUpgrading ODX to 6505.1 can prevent connections from being re-used. This has been resolved. Upgrading to 6505.1 can make custom measures and custom fields in Semantic Model instances change endpoint. This has been resolved.PortalAddressed issue in transferring instances.

New year, new features to make your TimeXtender life more enjoyable and productive! We're happy to announce the release of a new major version of TimeXtender (Desktop v. 6505.1) that includes all of the belated holiday gifts listed below. NewAutomatic data source creation in the ODX: When you map a data source connection to an ODX instance, a data source using the data source connection will automatically be created in the ODX. In addition to that, when you add a new data source connection you can now map a data source connection to an ODX instance right on the same page.  Test connection from the Portal: You can now test if the ODX can establish a connection to a data source when you add or edit a data source connection in the Portal. Improved step-by-step Get Started guide: We've created a new and improved step-by-step Get Started guide in the Portal. You can access it right from the Home page where it has its very own card. As you check off the steps, your progress is saved - on a company basis - so you can see how far you've come. And if you're already a TimeXtender champion, the card can be dismissed so it doesn't clutter up your Home page. New TimeXtender REST Provider: The brand new TimeXtender REST data source provider simplifies connection to REST-based data sources. Among other improvements, the new provider allows you to set up endpoints without fiddling with configuration files. Instances grouped by environment in Desktop: As an improvement to the multiple environments feature we added in our previous major release, instances are now grouped by environment in TimeXtender Desktop. We hope this will bring some peace to people who like things well organized! Generate end-to-end execution packages and tasks: To make it easier to set up a refresh of the data in a specific semantic model, you can now generate the data warehouse execution packages and ODX tasks that will update all data for a specific semantic model. When you make changes to the semantic model, you can regenerate the flow and the logic is smart enough to keep any customizations you made to the auto-generated objects. Calculation groups in semantic models: You can now add calculation groups to semantic models and deploy them to Tabular and PowerBI semantic endpoints. To make that work, we've added the 'discourage implicit measures' option to the endpoints. It defaults to 'automatic', which means 'true' when you've added calculation groups, and 'false' otherwise. Snippets in semantic models: It's now possible to add DAX, Qlik, and Tableau snippets, and use them in semantic custom fields, custom measures, and calculation group items. ChangedWe've tightened up the design of the add/edit data source connection pages in the Portal. In addition to the general improvements, some connections now have nice-to-have fields and categories hidden in an 'Advanced' section per default so you can set up a new connection faster.  We've improved the Desktop logic to more flawlessly support it when you rename instances in the Portal. In custom scripts in semantic models, you can now use the 'Value' parameter. Fixed PortalFixed an issue where users could see - but not access - instances that they hadn't been granted access to. Public job endpoints weren't able to handle unknown states. Endpoints were added out of order in the SSL form. Fixed issue with the "move customer" operation. Storage types weren't always loaded on the MDW form. Fixed floating info icon on SSL form. Fixed issue where the Portal throws a "not signed in" error - usually due to your token having expired - but then fails to route you back to sign in. The deployment target option for Analysis Services 2022 was missing from the Tabular SSL endpoint. Cloning a data source connection would route you to the original form, instead of the clone form. Disabling automatic firewall rules didn't always get handled correctly when handing out connections.DesktopFixed an issue with data lineage sometimes failing when trying to aggregate the display values in SQL Fixed an issue where the ODX service would sometimes fail to validate the data source connection version of TimeXtender enhanced and TimeXtender ADF transfer components causing an error. Updated some logic to better handle unsupported data sources instead of throwing an unclear error message. Fixed an issue where using an already created SQL database as storage for an ODX instance would reject the database due to the validation of the data storage version. Fixed issue with data lineage and reverse sign transformations not working Fixed an issue where using a dot (.) as the last character of a table name would cause executing a task in the ODX using a data lake to fail. The dot character will be replaced by an underscore when the dot is the last character of a folder name in the data lake. Fixed an issue deployment would fail when a source table DW_Id is mapped to a destination table DW_Id Fixed an issue where the TimeXtender BC365 online data source was failing to validate before inserting system fields during transfer. Fixed an issue where Synapse data warehouse would fail when adding a selection rule on a renamed field. Fixed issue setting up an incremental rule with year subtraction. Fixed an issue where generating documentation when only having an ODX open would throw an error. Fixed an issue where mapping would fail for tables that used system fields as column names. Fixed an issue where a table with multiple lookup fields would return incorrect results in Snowflake data warehouse. TimeXtender SAP Table data source provider:  Added support for DecimalFloatingPoint34 and DecimalFloatingPoint16 data types Fixed issue where fields starting with '/' could not be added to incremental rules Fixed issue where max. row setting was limiting number of data rows to be transferred Improved logging Fixed an issue where the default relation was not set correctly when relating tables in a semantic model. Optimized instance updates during task initialization

Today, we’ve published a minor release of TimeXtender Desktop (v. 6436.1) that contains the following changes:Fixed19801: Import settings from a previous version is not choosing latest version. Fixed an issue where it would choose the wrong latest version to import settings from. 19805: Missing check enabling Raw Only Fields to be added to a table on a different area. Fixed an issue where a missing validation enabled raw only fields to be added from one table to another. 19824: Upgrading to 6431.1 can make ODX data sources loose columns when using simple select. This has been resolved. 19852: Azure Data Factory does not work in version 13. The issue was fixed. Azure Data Factory data source connections need to be upgraded version 14.

Today, we’ve published a minor release of TimeXtender Desktop (v. 6431.1) that contains the following changes: FixedWhen a data warehouse had ADF transfer from ODX enabled, a validation would fail which caused tables with mapping sets to be unable to be deployed.

Today, we’ve published a minor release of TimeXtender Desktop (v. 6430.1) that contains the following changes: ChangedRemoved the ‘Copy to Instance’ feature from Desktop as this is now done in the Portal.FixedExecuting an execution package with an incrementally loaded table added to the Full Load objects list would do a wrong cast and throw an error.

And it's about time for a new release of TimeXtender! The new version (Desktop v. 6429.1) includes a bunch of much-requested and, dare we say, exciting features, that we hope will improve your day-to-day. It doesn't have to be crazy at work.NewAs with any innovative feature release, there may be some quirks along the way. Though we’ve done extensive initial testing, we encourage you to report any bugs you may find so we may release further improvements as rapidly as possible.Multiple environments and instance transfers in the Portal: You can now group instances in environments to keep everything nice and ordered. In addition to that, you can transfer the contents of one instance to another, enabling a true DEV -> TEST -> PROD workflow right in the Portal​​​​​   Data source "adapters" for selected ERP systems: We've added new data sources for Microsoft Dynamics 365 Finance & Operations ("AX") and Microsoft Dynamics 365 Business Central ("NAV") that make it easier for you to handle accounts as well as other functionality that make these systems easier to work with. In the Portal, you'll find them in the data sources list as "TimeXtender Dynamics 365 Business Central" and "TimeXtender Dynamics 365 Finance" with "- SQL Server" or "- Online" appended.   Improved support for Snowflake as a data warehouse: We've taken a big step towards supporting each and every TimeXtender feature when you use Snowflake as data warehouse storage. The newly supported features include incremental load, conditional lookup fields, field transformations, field validations, history tables, supernatural keys, and custom views. Aggregate tables, custom data, custom hash fields, junk dimensions, pre- & post-scripts, related records, and table inserts are not supported yet.    XPilot integrated in the Desktop: You'll now find a handy link to XPilot, our data integration chatbot, right from the toolbar. Try all the features for 14 days: You can now try all TimeXtender features for free for 14 days before you decide if you're ready to sign up for a paid subscription. The feature- and resource-limited Free tier has been retired. Automated migration from 20.10 to the newest version of TimeXtender: If you are still on the 20.10 branch of TimeXtender, you can now upgrade to the newest version without starting from scratch. The 20.10.45 release of TimeXtender can convert existing projects to cloud-based instances to minimize the work you need to do to move up.   ChangedWe've standardized terminology around instances and data source connections in the Portal. Among other things, we wanted to fix the common confusion around data sources. Now, in the Portal, you add "data sources connections" that can be used on "data sources" in the ODX in Desktop.FixedPortalOn the Instances card on the Home page, the instances as now ordered with the newest first. On the 'Add/editing data source connection' page, the left-side section navigation was not displayed. On the 'Add/editing data source connection' page, SSL secrets are now hidden. The Portal would show incorrect data source variable names. A data source connection would fail to save due to an incorrect validation error. In some cases, the activity list would fail to load or the pagination would break. The Customer Details page would be displayed for deleted customers. We've improved the loading of the Home page with better loading animations. If a company can't be moved, you'll be notified without the Move modal popping up.Desktop18959: Updated sql server 2022 assembly dependencies 18988: When executing an object in the data warehouse with ‘Data on demand’ enabled on the data source, the transfer from the data source to the ODX storage would not be visible in the log. Now, the transfer from the source has a separate entry in the log in the details for the "outbound" transfer. 19123: Fixed an issue with sql spatial types and sql server 2022 in the MDW. 19191: Added support for data source connections without descriptions. 19199: Deploying only modified tables was very slow while deploying all tables was faster. 19261: An issue where you cannot add fields to semantic model tables with custom fields has been resolved. 19265: Changed a label from "data area" to "data warehouse" in the Execution Server Configuration tool. 19269: Fixed an out of memory exception. 19304: Empty tables would be created when using SQL Server as ODX Storage. 19317: Optimize StepRowCountLoggingExecute.cs (logging of rows). The logic behind the Step Row Count has been optimized. 19323: Mapping same field to multiple fields in a MDW table from ADF not possible. Using Azure Data Factory transfer from ODX to MDW doesn't support mapping the same column from the ODX to multiple fields on the same table in the MDW. We have added a validation that blocks this scenario in a deploy/execute scenario. 19326: We fixed the issue with losing new lines when saving or updating a Query Table on ODX. 19343: Improved labeling of Edit MDW instances. 19358: The version number was sometimes replaced with a random word in the Copy to Instance dialog. 19367: We resolved an issue where, when adding a job, the color for an invalid selection did not get grayed out, and there was a misalignment on the control for validating an item. 19386: Fixed a scaling issue with the documentation template dialog 19400: Can't authenticate the D365 BC provider on creation. 19412: Fixed an issue with "show translations" not working on custom measures for Power BI premium. 19415: Fixed an issue where data formatting settings were not enabled on SSL fields for Power BI 19429: Removed unnecessary warnings in the ODX when synchronizing OLE DB based data sources 19457: Fixed an issue with remapping SSL table when the mapped MDW gets deleted. 19464: Added syntax highlighting for various scripts. 19505: Fixed an issue with clone fields and lookup transformation templates. 19519: There was an issue with incremental load into Azure Data Lake storage where the source type is handled as UniversalDataTypes.Datetime. This caused the incremental datetime value to be UTC + local time offset. 19526: Improved error message for when loading an instance fails. 19533: Added support for OAuth login during the add data source flow in the ODX. 19540: Fixed an issue with enabling 'Keep fields up-to-date' with XML data type fields. 19560: The ODX would continue transferring data even though the task was stopped in the ODX Execution Queue. 19562: Fixed an issue with running a job schedule set to "run once on this day". 19627: Fixed an issue where running execution packages with prioritization didn't work. 19678: Fixed an issue where deleting a data source in the ODX would not always do cleanup of its task history.