Skip to main content
Solved

Mapping set not working with custom fields


Forum|alt.badge.img+2

Hi,

I want to use mapping set to map several ODX tables with the same table structure to a single DW table.

The problem is that I also want to create additional “custom fields” in the DW table, and since these fields do not exist in any of the ODX tables, the mapping set excludes all the ODX tables and I am left with an empty DW table. Is there a work around to this? or am I perhaps doing something wrong?

This is my DW table:

 

The bolded fields with descriptions do not have mappings to them, they instead have custom transformations.

I have used “convert to mapping set” to get the mapping set, and then adjusted it so both tables match the mapping set rules.

As seen below, both tables are then excluded since neither have the custom fields.

 

Is it necessary that all fields have at least one mapping to them?

Best answer by pontus.berglund

Hi @Christian Hauggaard

Thank you for the example. It does indeed look identical to my situation. I am using version 6221.1, but I will upgrade it to the latest version and try again.

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

4 replies

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

Hi @pontus.berglund 

Which version of TimeXtender are you using?

I am not able to reproduce the issue in 6346.1.

I can create custom fields in my table containing a mapping set

I am also able to add a data selection rule similar to yours

 


Forum|alt.badge.img+2
  • Author
  • Contributor
  • 60 replies
  • Answer
  • October 19, 2023

Hi @Christian Hauggaard

Thank you for the example. It does indeed look identical to my situation. I am using version 6221.1, but I will upgrade it to the latest version and try again.


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • 1017 replies
  • October 23, 2023

Hi @pontus.berglund 

Please let us know if it made a difference using the newest version.


Forum|alt.badge.img+2

Hi @Thomas Lind, We updated to 6346.1 but the problem persists.

I will try to replicate the problem in my own setup with the latest version to see if that helps.


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