Skip to main content
Solved

Custom Data Selection in DSA layer in TX v20.x


I have a table X in the DSA layer from TX and I can't find the script to get the right output. 
 

There is a field FCL that possible have multiple records with different YearFrom and YearEnd. 

FCL   YearFrom   YearEnd
1        2010           2020
1        2021           2050
2        2010           2050 

 

I need a data selection rules that only imports from the ODX layer the FCL with the highest YeardEnd group by FCL

FCL   YearFrom   YearEnd
1        2021           2050
2        2010           2050 

 

Is there anyone who has a suggestion. The output from is table is userd as lookup table for another table in the same DSA layer. 

Best answer by nmo

@roland.peeters 

Something like this with a custom transformation on your sourcetable (you read everything in from the ODX) and then you use that field when doing lookups:

 

View original
Did this topic help you find an answer to your question?

5 replies

Forum|alt.badge.img+1
  • Contributor
  • 24 replies
  • May 14, 2025

I would probably just create a custom field with something like below and just add a fixed value to lookups with [Filter = 1] = 1

 

Alternatively, if your datasource supports managed queries you could do your filtering then as well


rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • 698 replies
  • May 14, 2025

Hi,

I would think a bit about whether you might ever need the raw data for future requirements. If so, you can load all the data and stage it to generate the output you need. One way would be to aggregate on FCL and Max YearEnd, lookup up the matching YearFrom.

If you know you will never need the raw data, the possible solutions depend on the version of TimeXtender. In TX Classic you could use a custom Data Selection rule to do more complex filtering source-side, in TDI you could use a new field like ​@nmo suggests.


We are working with TX v20 (Classic). I also need the rest of the fields in the (dim)-table as lookup to the fact-table. So i am affraid that aggregation is not the solution. 

I tried several filtering in the custom Data Selection, but it doesn't work. 
In our BI tool i would use the function  max(YearEnd for FCL) = YearEnd

This didn't work in TX. 

 


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Forum|alt.badge.img+1
  • Contributor
  • 24 replies
  • Answer
  • May 14, 2025

@roland.peeters 

Something like this with a custom transformation on your sourcetable (you read everything in from the ODX) and then you use that field when doing lookups:

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings