General

We are currently using TX to stage and merge multiple source systems to create a master list of items, customers, vendors, Open AR. Open AP, etc.  Currently, we are using the Data Export on the Semantic Layer to dump out entity data so that it can then be read in by D365 as delimited text files.  I am wondering if anybody knows if there is a way to direct connect to D365 so that TX serves as a source to a D365 system? Thanks, Greg  Laymon

Hello, I found a bug in TimeXtender Discovery Hub: When using both the features "Use hard deletes" and "Keep field values up-to-date", certain lines are not deleted, although they disappear in the source table. The following code gets generated to handle the delete process: DELETE V FROM [dbo].[f_data] V WHERE NOT EXISTS ( SELECT TOP 1 1 FROM [dbo].[f_data_PK] P WHERE P.[id] = V.[id] ) AND NOT EXISTS ( SELECT TOP 1 1 FROM [dbo].[f_data_R] R WHERE R.[id] = V.[id] ) This works correctly without the "Keep field-values up-to-date" feature. All rows that are not in the _PK table and that are not in the _R table get deleted. But there are rows that get updated by the "Keep field-values up-to-date" and land in the _R table, although they are not in the source table. This is why they  don't get deleted.

Hi, to configure the multiple environment setup I used the PDF (https://support.timextender.com/hc/en-us/articles/360001136526-How-to-configure-Multiple-Environments) , and everything works well when all the firewalls are turned off. We have opened port 10001 and 5001, but when the firewall is turned on, my DEV environment can't connect with the Production environment. My setup now is a Development server and a Production server. When I want to connect from Development to Production, I see the servers negotiating on port 10001 and 5001. But after that, they continue to work with a port in the 64xxx range (examples: 64135,64177,64281 etc) e.g. a random port. My firewall won't except this, and I would like to know if it is possible to work with a standard range / port so we can configure our firewall accordingly. Kind regards, Rogier

Hi guys,   Can someone elaborate the different options of table trunctation? I can't really find it in the help or e-learning.    We have set up an incremental load on a large table in the ODX, initially in simple mode. We found that the data after deployment & execution exists in the valid table and in the raw table, occupying twice the available storage of the original table size.    We then disabled simple mode and checked the truncate raw table before transfer. I now still see some records (not all of them) in the raw table. I guess I'll have to check "Empty raw table after data cleansing" to completely emtpy the raw table after reloading, but I can't really grasp the difference between these options.  

How can we configure TX to create non clusted indexes to  filegroup 1 and depending on the type of table create the table on filegroup 2, 3 or 4?We are running SQL 2008 R2 standard so we don't have the partitioning features.

Did anyone tried to rename or modify the source code on system fields from being 'customdata' based on the filename or business unit you are unloading a text or excel file? I would really love this as this source code is one of my primary keys and it's uniform irrespective of the business unit I unload the data becoz of excel docs being used.   https://support.timextender.com/hc/en-us/community/posts/205685383-Source-filename-for-Multiple-text-file-data-source  

Hello fellow TimeXtender users, We were wondering: is it worth upgrading from SQL 2014 to 2016 in the scenario where we use TX traditionally: stage - dw - cubes. Has anyone done it and have you seen performance improvements? Thanks! Wim CALM - Co