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

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

Tab order when using -prj xml-files

Hello!

I've been trying out the new version control feature in QV 10.

Since we are a small team working on the same document, this is a huge help for us.

But there seems to be something wrong with tab ordering when loading a document when some of the xml-files have been changed.

I made a small change for one tab. Changed the visibility setting from false to true in the xml-document. When I Open my qwv file all tabs ar orderd by their id instead of the order stored in the xml-document or qwv-document.

Is this a bug, or am I doing something wrong?

Thanks

/Henrik

5 Replies
Not applicable
Author

I came across the same problem.

It seems that Qlikview uses the order of sheets defined in the file Qlikview.txt to arrange tabs, not TopLayout.xml as one would expect. And the order of Tabs (Sheets) in Qlikview.txt is reset to alphabetical order every time you save the Document, whereas TopLayout.xml is altered to show the order you specified in the Document but is then ignored when you reopen the file.

A quick (but tedious) fix to that would be (re)naming the tabs alphabetically in accordance to the desired order.

Is the Qlikview team aware of this bug?

Thanks, Max

Not applicable
Author

AHA!!! So THAT is why my silly tabs kept getting re-arranged!!!

Beware that if you have a -prj folder and copy in a different version of your qvw above it, opening the qvw in QlikView will do really strange things. It looks like it tries to MERGE what's in the qvw with what's in the prj folder....

UGH! It could at least WARN you that it's going to do this!!!

Not applicable
Author

I have discovered this too - incredibly annoying for one and means that this version controlling functionality can definitely not be rolled to a live environment.

Any ideas if Qlikview are aware of this yet (Max's query has not been answered above) or if it is fixed in QV10 SR2?

Thanks, V

Not applicable
Author

Any ideas?? I have the same problem!

k

Not applicable
Author

Never mind... I've resolved it!