Skip to main content
To homepage To homepage

Dear all,

 

We have tx instaled on Azure and on premise. The version we are using is 20.10.52.64.

 

how is it possible that on the onpremise we can use the custom data selection rule and on Azure this screen is not appearing in the DSA?

The issue we are facing is that we want to limit that data we want to load in the odx when the raw table is being executed. Therefore we want to set a customized data selection tule on the mappings.

Why this option is not in Azure but it is there on the on premise?

We want to load / keep all data in the odx server and make a data selection rule in the DSA..

Imagine we are migrating from on premise and we want to show only 15 months of data instead of  10 years. Only if the customer is asking for it we will load it.  This is working on the on premise perfectly.

Now that we are migrating from on premise to azure we are missing the most used data selection rule. And the advised work around

 

Hi @jermaine.cotino 

Can you show the same image where it doesn’t allow for you to use it?

It is not possible to make custom conditions on all tables facing the ODX, but all other places it is possible.

This is my project with ODX.

DSA pointing at my ODX.

MDW pointing at DSA.

 

Here I got another project that do not use the ODX, but uses the BU staging database instead.

 

I also got a project where the database used is stored in Azure, it also works here.

I do use Direct Read between Bu, DSA and MDW so they can share the same database for better performance.

Hi Thomas

See the below screenshot.

 

 

Hi @jermaine.cotino,

Between ODX Server and data warehouse layers, it is not possible to add a custom data selection rule. You can use the ‘filter rows’ function on the data source in the ODX Server to limit the records ingested into your ODX, or you can add a separate raw data layer, similar to a business unit, between your ODX and DSA. 

Between data warehouse layers, you can apply custom data selection rules. 

While I'm not sure as to the reason the option is not available, I imagine it has to do with issues querying parquet files in a data lake using custom SQL.

Kind regards,

Andrew

Hi @jermaine.cotino 

As Andrew alludes to it is because you point at the ODX and it is not possible to do custom queries against a parquet file.

It is a deliberate choice. I think there is a feature suggestion for the change of this somewhere. Perhaps if you use SQL as the ODX store or something like that.

Reply


Terms and ConditionsCookie settings