Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

BugId QV-10094 "rename table" changed in QV12.10

See attached .qvw and example-data!

In QV11.20 this script executes fine. It return 2 fields "F.Year" and "F.Revenue"
In QV12.10SR3 the scrpt fails.

It seems the behavior of "rename table" has changed.



Workaround:


In QV12.10 set ErrorMode=0





Labels (3)
4 Replies
swuehl
MVP
MVP

The behaviour seems to have changed indeed.

IMHO, the new behaviour is 'correct', because the code tries to rename a non-existing source table to an already existing destination table name (in the 2nd / 3rd iteration of the loop). So I would expect to get an error.

Anonymous
Not applicable
Author

It was a very handy script to get short prefixes for your "Qualified" fields while having a normal tablename.

Anyway:

It's a undocumented change from QV11.20 to QV12.10, similar to the applymap-change in QV12 which they documented several ServiceReleases later.

--> I would expect qliktech to mention this in the releasenotes/documentation at least.

Let's see what they do with the bugid.

swuehl
MVP
MVP

Agreed.

BTW, thanks for sharing all these bug reports, Roland.

berndshexe
Partner - Contributor III
Partner - Contributor III

Thanks for your post!

I think it is a thing in the interpretation in loops.

We had an issue with an include in a for each loop.

up to Version 12.0 SR3 it worked:

for each f in filelist

...

$(Include=filename)

...


since 12.0 SR4 there has to be a semicolon:

for each f in filelist

...

$(Include=filename);

...

we didn't get a Bug ID, because the support says it is working as designed.

Regard,

Petra