When an ODX table is mapped to a DSA table you can now only use column filters. It is not possible to set a (custom) table filter.
example:
You can filter on "date GREATER OR EQUAL 2023-01-01"
but you can't use a filter like "field1 + field2 > 1000"
or a filter like TRIM (field) = 41 is not even possible.
+8Hi,
this is essentially:
Please also add upvotes there to get this prioritized.
I don't agree that these are the same things. They are alike, because both posts ask for a possibility to filter tables more flexibly. However one post wants to filter tables loading into the ODX storage (by using variables), the other filtering tables from the ODX storage into the DSA (by using custom queries).
Both are things I would like to be able to do, by the way.
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?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
