Skip to main content
To homepage To homepage

Hi 

A customer of ours is noticing that the order in which TX is deploying and executing the datawarehouses they have causes empty tables. 

They are using TX Classic without an ODX, all sources are in Business Units. From the business units data flows to the DSA datawarehouse. From there it flows to the MDW datawarehouse and finally the data flows to the Delivery datawarehouse layer.

When making changes to tables in the MDW layer that affect tables in the Delivery layer and then performing a deploy & execute you can clearly see that the affected tables in the Delivery layer are handled first followed by de MDW layer.

This also happens in the scheduled executions causing empty tables and having to execute the Delivery layer by hand. 

Is there a way to change this order?

Hi ​@rbrandsma 

The program deploys the tables in the order of top to bottom, if no rules are being used.

Deploying shouldn’t have an effect regarding the order, but this is really important for executions.

I would check that all the tables in the MDW is properly related, especially if they are custom tables or views. The execution package also needs to be set up in a way that allows it to run in the order that will make sure it ends with no empty tables.

Can you share an image of the execution package you run for this?

Terms and ConditionsCookie settingsAccessibility statement