Mapping set not working on renamed columns

Hi @KajEmergo 

I don’t think you can change the name at all it needs to be exactly the same as in the source.

Is that the case now when it do not work or did you manually change the names while having a different field mapped?

Hi @Thomas Lind,

That's a pity. This way mapping sets forces you to keep the names in your DSA table like they are in the source. Sometimes these can be quite messy, so it would be great to have the mapping sets working properly while renaming the fields in the DSA.

Right now, I am forced to manually map the tables using the ‘smart synchronize option’. That works for me, but when you have a lot of data sources with the same structure this can be a lot of work.

Best regards,

Kaj

Hi @KajEmergo 

You mean it should be better at merging tables so there can be slight differences between the names and it will still be seen as the same?

@Thomas Lind, not really like differences between the names from the two different ODX tables. But the mapping set should be able to add a second mapping to a DSA table (after I renamed columns) and still keep the field mapping, like I did below:

My steps were like this:

1. Create the table in DSA by manually dragging the first ODX table to DSA
2. Rename fields in DSA
3. Add second ODX table to DSA by using ‘smart synchronize’

I would like to convert the original mapping to a mapping set in step 3, but then the field mappings break. It would be great if the mapping set detects the first mapping and the changed column names just like a smart synchronize does when manually mapping a second table to an existing DSA table.

Hope that this is clear enough.

Best,

Kaj

Hi @KajEmergo 

I thought the field names had changed in one of the sources

This seems like an idea then.

I guess the issue is how the table with the name change would know what it should merge with.

To get mapping set to work again, you need to give it the original name back and it will be able to merge the tables.