Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us at Qlik Connect 2026 in Orlando, April 13–15: Register Here!
cancel
Showing results for 
Search instead for 
Did you mean: 
SudhaX
Employee
Employee

Bookmark creationDate is null after creation - when does it get populated?

Hi all,

 

In one of our projects we are fetching bookmark details using the BookmarkList and noticed there is a creationDate field available in qMeta. using this field we are able to sort list based on creationDate. 

 

We are creating bookmarks using app.bookmark.create() via the Capability API and we are not passing any creationDate at the time of creation. Even when we tried explicitly adding it, the value starts as null.

 

What we observed is that approximately 10 minutes after the bookmark is created, creationDate gets automatically updated and we can see the actual date populated.

 

Can anyone explain what triggers this update? Is it an app save, engine processing, or a scheduled job on Qlik's side?

 

Thanks!

Labels (2)
1 Reply
hugo_andrade
Partner - Specialist
Partner - Specialist

Hi @SudhaX ,

Welcome to the Qlik Community!

From the docs, app.bookmark.create() only takes title, description, and optional sheetId. There is no supported parameter to set creationDate yourself, so that value is not meant to come from the client call. It looks like creationDate is system-managed metadata rather than something populated immediately by the Capability API call itself.

https://help.qlik.com/en-US/sense-developer/November2024/Subsystems/APIs/Content/Sense_ClientAPIs/Ca... 

I could not find any Qlik doc that says this is tied to an app save, a specific engine event, or a documented scheduled job. The official bookmark docs show how to create and list bookmarks, but they do not describe when creationDate is stamped.

So at a practical level, I would treat creationDate as eventually consistent metadata, not something guaranteed to be present immediately after create() returns. If you need it right after creation, the safest next step is to store your own timestamp alongside the workflow instead of relying on qMeta.creationDate in the first few minutes.

Hope this helps. Please give it a like, mark it as Helpful or Solution if that was the case.

Live and Breathe Qlik & AWS.
Follow me on my LinkedIn | Know IPC Global at ipc-global.com