Promoting columns in the sort tab not getting saved

[linoyel]

Hey,

I have a straight table with dimensions and expressions, and I want it to be sorted by one of the expressions.

So I promoted this expression to the highest priority on the sort tab.

Then I saved the document.

But when I open it again - the sort order returns to the original one!

Can someone tell me why is that happening and how to fix it?

Thanks!

[linoyel]

If you save the document after sorting and the report remain OPEN - then next time you open the document everything is OK.

But I need it to be closed on opening.

So I need the document to be saved after pressing on "Hide goals report".

And here is a problem.

[linoyel]

Where I can contact support?...

[ashfaq_haseeb]

HI,

For that you need to have a valid contract with Qlik.

You can log a case via customer portal or partner.

Depending upon your relation with Qlik.

Or contact your nearest partner for the same

Have  a look at below post

QlikView Support - Business Intelligence (BI) Reporting Software Solutions | Qlik

Or you may reach them on support@qlik.com

Regards

ASHFAQ

[linoyel]

Thank you very much for the info!

[#6]

Hi,

Working fine for me.

PFA..

Thanks

[linoyel]

Hi Ankit,

If you open the document you've attached, you'll get it all messed up again...

[#8]

Hi,

I have just checked downloaded it and seems fine to me.

Thanks

[linoyel · Accepted solution]

I've wrote about this issue to the Qlik Support and that's the answer I've got from them:

Dear Linoy,

I have tested the issue with the sample QVW you have provided me. I am able to replicate the issue and I also confirm that the workaround that tested is valid as well. Please note that the client build version of desktop you are currently using 11.20.12018 (11.20 SR 3) is no longer patchable.

  I was am able to replicate the issue in 11.20 SR 7 our latest version of QV developer. I can log this issue as a bug, just know that it will probably get a low priority and the timetable for if/when the bug is approved and fixed is will be unknown.

So it's a bug...

I hope they fix it soon.

[#10]

Hi Linoy,

Thanks for sharing the update:).