Skip to main content
To homepage To homepage
Solved

Exclude DW_ID from Primary Key on Database

P
Starter
Forum|alt.badge.img

Hey everyone,

I have the following question:

Is it possible, at the database level, to set the primary key to the one selected in TX (e.g., "Umkod_ID") instead of the default "DW_ID"?

The issue arises because we access our table via PowerApps, and since the app existed beforehand, references in the code were already predefined. Currently, the app's primary key is set to the "Umkod_ID" field of the table. However, in our database, the primary key is set to the system field "DW_ID."


 

Since this table is only loaded once and no transformations occur, the system fields are not particularly important to us in this case.

We resolved this issue by manually populating the table, but I am curious if anyone knows a workaround that could be applied to similar cases in the future.

Best answer by rory.smith

Hi,

as far as I am aware all TimeXtender tables have a clustered primary key on DW_Id. You can of course generate a view that is unique on the business key to facilitate your usecase.

View original
Did this topic help you find an answer to your question?

2 replies

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • rory.smith
  • TimeXtender Xpert
  • 686 replies
  • Answer
  • April 3, 2025

Hi,

as far as I am aware all TimeXtender tables have a clustered primary key on DW_Id. You can of course generate a view that is unique on the business key to facilitate your usecase.

P
1 person likes this
  • P
    philippus.asefaw
P
Starter
Forum|alt.badge.img

 Hi Rory,

thanks for the input!
I also came across the clustered pk on DW_Id somewhere in the Knowledge Base and thought that there maybe could be a way to deactivate this functionality…

I see the point you are trying to make with the View and see it as a probable solution.

However I probabIy explained our use case in a misleading fashion by saying:

 

Since this table is only loaded once and no transformations occur, the system fields are not particularly important to us in this case.

 

What I meant was that there are no transformations or whatsoever made in Timextender itself… however our table could be updated by an App in PowerApps which would make the workaround by using a View unfortunate.
And following this keep my safety net and in worst case roll it back to the first version through TX then.

This is just me being a bit too organized and wishing I could oversee my whole landscape through TX ^^

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings