Skip to main content
To homepage To homepage

I am loading a fact table from a staging table, both are regular data warehouse tables. When I create a data selection rule on the mapping table, I'm unable to select the conditional lookup fields or the system fields from the source table:

 

 

TX Version is 6590.1. In legacy TX, it is possible to select the conditional lookup fields and system fields for creating selection rules:

 

We have implemented a workaround where we create an extra field in the DSA table that has a transformation that fills it with the value of the conditional lookup field. In turn, this extra field does show up in the selection rule fields because it is a regular field. But this is not a very nice or future-proof solution.

Is this an intentional change and if so, can you explain why? Or perhaps this is a bug in TX SAAS?

Hi @wouter.goslinga ,

if you take the field into the MDW table you should be able to select it if you make the Data Selection rule at the table level instead of at the mapping level as another work-around option. If your MDW table is not simple-mode you could consider using raw-only on the field if you only use it for filtering to at least spare the space in the valid table.

I agree this is cumbersome and I'm not sure there is a valid functional reason for this.

@rory.smith thanks and I agree but the big difference between a filter on the target table and a filter on the mapping is where the filter is applied, i.e. before or after the transfer. In this case I want it to be on the mapping so I can restrict the number of records being transferred.

It feels a bit strange that existing funtionality is being removed, looks like a bug to me.

@wouter.goslinga For me it’s a bug too

Thanks for reporting this issue. The product team are working on a fix. Please see release notes for upcoming fix 

@wouter.goslinga  A fix has been released for this in:

  • In the Selection Rules pane on mapping tables, some fields, including conditional lookup fields and system fields, would be missing for tables from another data area.

Reply


Terms and ConditionsCookie settings