Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I am using the rename function in my script
Binary [..\..\2_qvd_layer\publisher\Generator_DataModel_Build.qvw];
New_Fields:
mapping LOAD
Old_Field,
New_Field
FROM
[..\Data\New_Field2.xls]
(biff, embedded labels, table is Sheet2$);
rename Fields using New_Fields;
This works fine so far, but unfortunately my multibox gets no updated with the new field names
has anyone a solution for this? thanks.
very strange, after using MAP, I changed it back to Rename and now it is working
Hi,
Can you try "MAP" field names instead of Rename ?
Thank!
I think you will have to manually go in to change the field names to the new one....
but this can not the first opportunity, I tried it in a really small app, with only 5 field, there it worked perfectly, multiboxes, expressions everywhere the name changed, therefore I do not understand this issue.
this is not working, nothing has changed when using MAP
Well QlikView tries to help us when the number of fields that have changed names are 1 or 2 (never seen it happen with 5 fields, but all 5 field names were changing?) With more than 1 or 2 field names, QlikView doesn't really know which old field name belongs to which new field name. In order to not mess it up, it leaves it for the users to make that change.
I guess I see why you would think that it should know because you have told it in the script that a changes to Z and b changes to X... but I don't really think it use that information when changing the field names.
very strange, after using MAP, I changed it back to Rename and now it is working
This is a known limitation:
https://community.qlik.com/thread/53038
If there's too many things for you to rename one at a time, and the method suggest in the above link does isn't applicable for you, you could try writing code that will rename one field at a time (use a variable set to 1, get only that number from the rename file, and then increment the variable) and then run that repeatedly. That might work as for each run only a single field will be renamed.