Document in server and in client is not the same

[linoyel]

Hey all,

I'm facing a weird issue with QV document:

there is a difference in a column sort if I open a certain QV document in server or in client.

In server the column is in a descending order, while when opening the exact same document in client - this column is sorted in an ascending way, while all rest of the data is the same.

What can cause this issue?

How to fix it?

Thanks!

P.S. The sort problem is not with a specific column, it's actually with the whole document sorting...

[linoyel]

Hi Peter, the user can not change the document at all. Users don't have any developer permissions.

I by myself ran the job which reloads the documents and puts it in the Shared  drive, and then I opened it from the server, and then I opened it from the client  - and there was a sort order difference.

[linoyel]

All right! Now I see the access point and the "view details" you were talking about... it's just that clients don't open docs from here but from QV client itself --> open in server.

I'll try to remove "last document state" and see what happens.

Where I can access server setup options?

[Peter_Cammaert]

QMC = QlikView Management Console.

Open http: //yourservername:4780/qmc/default.htm

You may have to configure yourself as QlikView Administrator first. To do so, add your windows AD account to the QlikView Administrators local group of the QlikView Server machine.

Peter

[#5]

Press Ctrl+Shift+B and remove any user bookmark related to sorting if any

[stevedark]

The Access Point is the simplest way to deploy to users who don't need to change anything.  Nothing needs to be installed on their machines.

If they open using Open In Server then some of their own settings (including sort orders) will be persisted between sessions.

[Peter_Cammaert]

So the difference is between a document opened with File->Open and navigate to the fileshare to pick your copied document, and a document opened with File->Open in server... upon which you get these green lists of documents form which you pick your QVS document.

OK, then the trick with Remove Last Document State will fix it. Because the QlikView Server keeps a log of all your selections and settings each time you visit the QVS, and will merge them back into your view of a reloaded document each time you visit it using Open in server... Just like during a visit to the access point...

Good luck,

Peter

[linoyel]

Some information that might be important to know:

1. The document reloading job is not from the QV management console but from Windows scheduler.

2. When I open http://my-server-name/qlikview/ in a browser, I see the file icon in the access point but the last loading date is very old (August 2013), and when I press on the icon to open it - it says access denied, there are no CALs (no permissions).
The company management says that anyway they are not going to change the policy, and users will continue accessing QV documents through local QV clients installed on their computers, and not from access point...

Anyway, why do you think access point doesn't show the last file version (from today), and why it's impossible to open it from there? What would you suggest to do?

[linoyel]

Yeah, you get it right...

I see the document in Access Point, but it's version (Last Update) is very old and it's impossible to open it from Access Point anyway. As I understand, I can do the trick with Remove Last Document State only from Access Point, right?
I just think that first I need to unedstand why it shows last year's version and it's impossible to open it from there (but possible to open from local client --> QV --> open in server)...

[Peter_Cammaert]

I cannot immediately think of a reason for this new odd phenomenon. Perhaps you are using an Alternate Identity in your Open in Server dialog?

In theory, there is no difference whatsoever between getting access to and openeing a document from the AccessPoint, and doing the same via Open in Server. Both methods use Windows identities to authenticate, use these identities to figure out what documents you can see, and use these identities to tell the document who you are and how it should reduce data (in case you're using Section Access with NTNAME). The clients are different, b ut the rest stays the same.

Peter

[#11]

Hey,

I've got a way to avoid this bug : sorting by expression, it will keep the 'descending' setting.

Nicolas