how to see a qvw "opened in server" by another user

[dadumas]

Hi,

A user has done an "open in server" on a qlikview doc, and made changes using a leased license  (when he opened in server).  The intention was to let him make changes to a COPY of the doc, and then I would copy those changes (copy sheet objects) from his copy into the "regular" version, and then publish out the regular version. 

He has made modifications in place (not to a copy).  At this point, I cannot open his "version"of the document (bad). Also, on accesspoint he can only see his version (bad). Everyone else sees the "regular" version (good). 

Questions:  How can:

1.  He copy out his version to another name so that I can use as I had originally intended above?

2. He "release himself" from his version on the server?

I have read that its possible for me to "open in server" his version, and then copy over the objects as I originally intended.  However, that requires him giving me his login credentials which he does not want to do.

I have not worked in a "multi-developer" environment using a single qvw - maybe this is something simple to work out

Thanks,

Dave

[Peter_Cammaert · Accepted solution]

Intro:

The QV Desktop menu entry "Open in server..." causes QV Desktop to start acting as an AccessPoint client, and as a consequency it will show all limitations of an AccessPoint client. In short: no saving, no editing scripts, no reloading, just the things you can do in an Ajax client but in the context of a Windows UI.

When you say that this user makes changes to the document, in reality the user is not changing anything because what is coming from the published QVW file is immutable in the AccessPoint. On top of that, the QVW cannot be changed by anyone from within the AccessPoint.

Then where do these new objects and sheets come from, and why are they refusing to act like regular object additions to a regular QVW file? All stuff that you add to a published document from within the AccessPoint (indeed, even when using Open in server in QV Desktop) is kept by the server as so called Server Objects and stored in separate files in the Docment root. Each document will get a Shared file, alongside the Meta file and the original published QVW. When this user opens the document in a new session, the QlikView server will make sure to load all visible sheets/objects from the original QVW, and combine them with whatever server object the user created before in the AP. The server gives you the impression that all objects have s single source, but that's not the case.

Newly created server objects by default are only visible to the user that created them in the first place. That user can however share these objects with others through a featrue called "The repository". Nobody else will be able to import these objects, unless they are shared with those users. When shared, these objects will not appear automatically in their copy of the same document. Instead, they'll have to import them from the Repository before they become visible and usable.

While you may have thought otherwise, "Open in server.." is NOT a collaboration feature for developers. There is no such thing in QlikView..

With respect to your questions:

1. See repository remarks above. You already mentioned the easiest approach (using his/her credentials to open an AP session and copying server objects to the QVW) as being unacceptable.
2. If this user doesn't want to see these server objects anymore, he/she has to delete them. If your QlikView Admin feels confident about deleting server objects by a specific user, he/she can also do this in the QMC.

and with respect to so-called multi-developer environment:

• QlikView doesn't offer ready-to-use features for managing documents in a multi-developer environment, except by providing hooks for integration in a VCS. I guess because that's not really the core business of a BI company and other solutions already exist that do a good job here with all the flexibility that you prefer to get..

Best,

Peter

[dadumas]

Peter:

This portion of your below sums it up.  Thanks.  I was not aware of not being able to "save out" another copy while in "open in server".  As you say, "open in server" is just a "windows version" of editing a users own "shared copy" on the published document in the QV server.  Not sure if I worded that right.  Sounds like the user must (1) allow me to open with his credentials to copy his objects to the original document (that i use to develop in the SourceDocuments folder) and (2) when I am done, he needs to delete his added objects. 

Thanks!

Dave

The QV Desktop menu entry "Open in server..." causes QV Desktop to start acting as an AccessPoint client, and as a consequency it will show all limitations of an AccessPoint client. In short: no saving, no editing scripts, no reloading, just the things you can do in an Ajax client but in the context of a Windows UI.

When you say that this user makes changes to the document, in reality the user is not changing anything because what is coming from the published QVW file is immutable in the AccessPoint. On top of that, the QVW cannot be changed by anyone from within the AccessPoint.

[Peter_Cammaert]

My reply contained a second method to extract Server objects and plant them in the original QVW. If the user shares the objects in question with you, and you have access to this document in the AP, you can open the repository (10th icon from the left in the Ajax client, looks like a little bar chart) and place the user's objects in your own document. Then you can copy paste them immediately in the opened QVW.

Note that you cannot copy entire sheets. Actually you cannot copy/paste sheets at all, only individual objects.

[dadumas]

I opened the accesspoint document, clicked on the repository, and tried to drag a chart from there into the QV desktop development client with the  Source document opened (NOT "open in server").  This does not work, so I an confused as how to copy an object from accesspoint doc into a QV development client document.

[dadumas]

I think this is what I need to do:

1.  user shares new desired objects

2.  I use the repository and copy objects into my QV document using accesspoint

3.  In the devleopment cient, I "open in server", and then copy objects into the unpublished QV doc also open in the dev client.

Prior to publishing:

4.  I remove all copies of those shared objects in accesspoint (my user copy)

5.  user removes all copies of those shared objects in accesspoint (his user copy)

6  These shared objects ow no longer exist (good)

7.  I republish the now modified QV document

Everyone will see the new objects as they are part of the published doc, and since they are moved from "mine and his user specific" copies, we will see the server versions.

I will let you know.

Dave

[rwunderlich]

You have the general flow correct. Let me suggest a couple of options that may make the process easier.

For step #2, instead of using the Ajax client with AccessPoint, use "Open in Server" from the Desktop client. Use the "Collaboration pane" (F2) to access the objects the user shared with you.

Instead of having the user share and manage the objects, you can take ownership of the objects from the user, and also delete objects, from the QMC Users, Server Objects pane.

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

[dadumas]

Even better - I will try that!

Thanks

Dave

[dadumas]

That worked - thanks Rob!