Unanswered questions

Need help with TimeXtender data transformation issue. We're pulling sales data from SQL Server but getting errors during the transform step. The source has decimal values but TimeXtender seems to be reading them as text.Also need to set up a simple incremental load based on ModifiedDate field. Should be 2-3 hours remote work to fix the data types and configure the incremental logic.Need working by Tuesday for our weekly data refresh.Please Contact Me Asap.

I am having issues with decimal numbers in my Power BI model created with TimeXtender XMLA endpoint (version 7026.1).No matter the precision of my datatype on SQL server it seems like all values are forced into a rounded 4 decimal size. Is there a setting hiding somewhere to prevent this behavior?Below are examples or test data to demonstrate the behavior.Inspecting the model with tabular editor it seems all decimal fields are stored as fixed decimal rather than the expected double Test data Result in Power BI 

I have an issue, and i have not been able to identify if this is a TX issue or a DWH issue.This is how TX is set up:I have a MS PowerApp that writes to the APP database.I can see that the records are in the DWH, like in the table below.  I have confirmed that the entetried are in APP-stack.At 07:30 in the morning, execution package runs, then this happens:Meaning, the DW_ID that were previously Bob’s and Marlen’s are now overwritten by Kim and Tom.There are no traced of DW_ID 101 and 103 being registrered by Bob and Marlen either in ODX or in DSA.I dont know if it happens before the execution job runs, during or after. I have been scratching my head for the past couple of weeks.

We are using the provider Azure Data Factory - SQL Server for a lof connections where the instances for these connections contains almost the same data but each time another customer. What we have noticed when the incremental load is setup to look at a datetime field called DW_MODIFIED_date. it will never load that 1 record which is in the table. When I exclude that table from the incremental load then I have 1 record loaded.When I include the table again in the incremental load it is removing the first folder from the previous load and don’t write a new file because it was not updated.When I remove the folder from the container and I incremental load that client table again I get no record at al while it should be the first load. Even if the incremental load is on and there is no file  then I expect to have in the initial load the data.

I’m using TimeXtender REST Data Source v10.2.0.0 with two endpoints: A static endpoint that returns a list of IDs. A dynamic endpoint that retrieves additional data for those IDs. The problem is that not all IDs from the first endpoint exist in the second. When the dynamic endpoint tries a ‘non-existent ID’, the API returns a 500 server error, stopping the data transfer.This is an external API, so I have no control over it. From what I can see, the datasource provider doesn’t offer error handling (like try/catch or “skip if failed”).I could create a curated list of valid IDs, but there are thousands of IDs that can change at any time, making this impractical. I could also ask the API provider to return empty JSONs instead of errors, but I’d prefer to handle it on my side.Any advice?

What it’s the reason to this message:It would very useful to be able to do it.

Hello,Is it possible to Extract data from an existing Lakehouse into a Prepare instance without needing to move it into the TimeXtender Ingest instance? The use case is to avoid replicating the data again, if the customer has already ingested data into a data lake or Lakehouse.Thanks in advanceTim

Hi, I’m trying to connect to a API using Timextender REST version 7.1.0.0 but my result is only one row of data. In Postman I get much more data. It might be because the API returns JSONL and TX tries to handle it as JSON. I’m trying to convert it to Text but it still doesn’t work.  Earlier I managed to complete the goal in Power Query even with pagination.  Now I’ve hit a brick wall and I need your help to proceed. My result in ODX:  My result in Postman:Here’s my connection profile:{  "Name": "MixPanel",  "Description": "",  "Provider": {    "TemplateId": "d4aa4001-fd7b-4c65-b76d-f9710d551c1e",    "DisplayName": "TimeXtender REST",    "ProviderVersion": "7.1.0.0",    "X64BitVersion": true,    "ProviderType": 6  },  "RestProperties": {    "Pills": [      {        "Name": "Authentication",        "Description": "Configure authentication settings to securely access the API using tokens, keys, or other credentials.",        "Id": "rest-general-authentication",        "IsSelected": true 

Hi there! We have had a small problem recently whereas Table A is on the staging/DSA layer and contains the following columns: Column 1 (PK)Column 2 (PK)Column 3Column 4 … etcNow this table has three sources - three Business Central instances. In two of the sources the original order of columns is Column 1, Column 2 but in the third source the order is Column 2, Column 1.We get the following error when incremental load is enabled:  "TIMEXTENDER COPY DATA LOOP", "Failure happened on 'Sink' side, Column 2 contains an invalid value. We have been able to manage this error previously by ordering the columns in the same way as in the source.However, now the sources have different orders of the columns and therefore not possible to use that way to get around this. Any ideas or suggestions?