Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
When I create my own server objects (charts, tables etc) they sometimes revert to their original position the next time I log in. It seems to be happening randomly - not related to a particular qvw, user or type of object.
Is there a setting that controls this or could it be a problem with the server or shared folder reaching capacity?
I've found that this happens in one specific scenario: when you are connecting to AccessPoint via QlikView Desktop and you clone an existing object (one built into the qvw).
When you clone the object it will create the new object 10 pixels to the right and 10 pixels down from the original object. If you then move the new cloned object (either by dragging it or adjusting the object coordinates) it will appear to move OK, but when you close your session and re-open it the object will revert back to the original position (10 pixels away from the original).
So the solution is to not clone objects when connected to AccessPoint. Just copy and paste them. You can copy any existing cloned objects and then delete the cloned object to fix any outstanding problems.
There is no control also no settings for capacity. This issue is know in Qlikview , But it's very well maintained in Qliksense.
I've found that this happens in one specific scenario: when you are connecting to AccessPoint via QlikView Desktop and you clone an existing object (one built into the qvw).
When you clone the object it will create the new object 10 pixels to the right and 10 pixels down from the original object. If you then move the new cloned object (either by dragging it or adjusting the object coordinates) it will appear to move OK, but when you close your session and re-open it the object will revert back to the original position (10 pixels away from the original).
So the solution is to not clone objects when connected to AccessPoint. Just copy and paste them. You can copy any existing cloned objects and then delete the cloned object to fix any outstanding problems.
Update: Qlik have raised this as a bug