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

Announcements
Now accepting applications for the Qlik Luminary and Partner Ambassador Programs: Apply by July 6!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Rename Field throws error message after Service Release update

Hi @all,

after an update from QV 10 SR2 to SR5, one dashboard gives me an error on reload:

"New field name already exists!

RENAME Field A to B"

It's correct, the field really already exist.

I'm wondering why this error message didn't come up in former version. Nothing changed on that dashboard. Is it possible that QlikView behaviour changed in that area?

Labels (1)
1 Solution

Accepted Solutions
Not applicable
Author

1 Reply
Not applicable
Author