Skip to main content

TX allows to add data selection rules over calculated fields but gets an error in execute

  • February 21, 2023
  • 6 replies
  • 50 views

rvgfox
Problem Solver
Forum|alt.badge.img+4
  • Problem Solver
  • 229 replies

As you can see in the screenshot, I think that this situation must be controled:

 

6 replies

  • Contributor
  • 78 replies
  • February 21, 2023

How did you actually manage to select a field in your selection rule, that is not available in your mapped (source) table?


rvgfox
Problem Solver
Forum|alt.badge.img+4
  • Author
  • Problem Solver
  • 229 replies
  • February 21, 2023

@RLB That’s the problem, TX allows that:

 


  • Contributor
  • 78 replies
  • February 21, 2023

Very interesting! I believe the Data Selection Rules panel should only list the columns that have a mapping to the source table. In my TX environment that is actually what I'm seeing.

I'll be following this.


rvgfox
Problem Solver
Forum|alt.badge.img+4
  • Author
  • Problem Solver
  • 229 replies
  • February 21, 2023

@RLB That screenshots are for the new version:

 


rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • 684 replies
  • February 22, 2023

Even worse, if you implement such a Data Selection Rule on an incremental table that has already been loaded to DSA from ODX (ADLS) it may work until you run an explicit full load.


rvgfox
Problem Solver
Forum|alt.badge.img+4
  • Author
  • Problem Solver
  • 229 replies
  • February 22, 2023

Definitely it’s an error that must be controled


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