AFAIK there are three possible routes to take, of which only one I trust to produce decent output (1st one)
- Powertools: export the notes to xml using the Shared File Viewer Powertool. Then try to decode anything that looks like a binary block. Probably encoded in Base64. This is the only method that I think has the best chance of success...
- QMS API: not sure if there is any API method available at all to manipulate or export Server objects, but there could be something present that I don't know about.
- QlikView DOM & Macro API (in QV Desktop or OCX): I give this one only a tiny chance. Or in other words, I'm almost sure that Server objects cannot be accessed through the Macro API. But you never know
Peter, Thanks for the suggestion of exporting to XML from the SharedFileViewer. That allowed me to figure out what the space was being used for.
When you create a bookmark, you have options to:
- Save selections
- Include Layout State
- Include Scroll postions
Apparently, the bookmark created by "Take Snapshot" utilizes all these options (under the covers, you don't actually get a choice). Selections takes a relatively small amount of space dependent on number of selected fields and values. Layout state on the other hand, captures several pieces of information about every object in the app. The customer app I was looking at has 1000 objects, hence the large bookmark size.
I learned something new. There is significant .shared file resource used when using "Include Layout State".