Hi @anders.e.jonsson 

The feature used in LTS is not made in TDI yet. There is an idea for it though.

I guess you could maybe have different data sources in each environment with the same name that then contain different data, but besides that I got no ideas.

Hi,

if you split your environments across VMs you can also use the machine name in a variable though you can only use this in a Custom Data Selection rule and not in a Mapping Data Selection Rule.

Thanks Rory,

I saw that. Unfortunately it’s the same machine and instance for both the Dev and Test environments.

BR
Anders

Hi,

If I read it correctly we are talking about a system variable which is needed to create a (dynamic) data selection rule for a specific environment (DEV) for loading a limit amount of data to the DSA.

On premise Solution:

We have this working on 2 different servers. a DEV/TEST and a PROD server by using the Instance Variable in the menu tools to determine which project you are even it is on the same server and the same instance because we spilt the databases in DEV, TST and PROD and we give the environments the same name.

Therefore it is easy to create the dynamic rule based on the project you have opened.

For the on premise versions of TX, you can use the environment name

For TX Data Integration (Cloud version), you can use the ‘database name’. I ques, DEV, TEST and PROD environments have different databases.

After the migration all scripts are still working as before.

Last but not least you can put a custom data selection rule on mapping because then the selection of the data to be retrieved will be done before loading it in the raw table.

When the custom data selection rule is on the table TX will first load all data into the raw table then applies the data selection rule to the valid table.

If you have a small dataset then this will not be noticed, but if you have in the source 10 years of data for 20 different customers and only one customer is asking for more data, than this will be noticed if you do not have the custom data selection rule in place on the mapping.

By putting the custom data selection rule on the mapping you will only load the data that is in your selection rule to the raw table.

One note, the custom data selection rule cannot be set on when the mapping is done from the odx server to the first layer in Azure (SQL Server). This custom data selection rule feature is available from the first layer after the data is loaded from the odx server.