Skip to main content
To homepage To homepage

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.

Hi ​@aftabp 

The DW_Id value is given on the first execution of the DSA_App.Table. It will not change this due to it being a autogenerated field and it running with slowly changing dimensions.

In all the other tables the DW_Id can change on each execution and may not point at the same data.

You are still required to set a field to be the natural key. What is that?

​@Thomas Lind 

There is a column containing a unique occurances (carNoPlate), so that is my Natural Key.

I can see in the App that it picks up the carNoPlate. I have also checked with the source system, the values in the carNoPlate are always unique. 

 

Also, its not that the enteries always disappears. Most of the times they dont.

I have look at the table again, and i have a theory.

For startes, my Natural Key for History settings is carNoPlate, and SCD2 is dateTime

Here is a small extraction of the submitted timestamps (dateTime)

Several enteries have the same timestamp, and then there are some that are very close to eachother

I have used Datatime as the variable type in TX. May be i should use DataTime2 !

 

 

Terms and ConditionsCookie settings