Hi Inactive User ,
Try "uniqueId" instead of "id".
The "uniqueId" is a community-wide unique message id and corresponds to what you're seeing in the URL. The "id" is a board-specific message id.
Hi Inactive User ,
Try "uniqueId" instead of "id".
The "uniqueId" is a community-wide unique message id and corresponds to what you're seeing in the URL. The "id" is a board-specific message id.
Thanks, I must've missed that in the context objects docs.
AdamN this was very helpful. Is that only for MESSAGE ID's though? Or is that the same for topic/tkb article/blog ID's - they are globally unique? For example: http://community.blah.com/t5/Interactive-Lessons/Inputting-Data-into-Your-Workflow/ta-p/731can we know with certainty that "731" is unique globally? Or does your solution only pertain to messages/replies, and not topics/articles/etc?
Hi TreyWaddell ,
page.context.message.id should always give a node-relative message id, whereas page.context.message.uniqueId should always give a globally unique message id.
The thing to be careful about is which message is actually in context. This is typically dependent on the page URL. So within a thread, there are URLs that correspond to each individual message (i.e. permalink). And if you use that URL, that will be the message in context.
If you always want the root/topic message regardless of which message is in context, you can try to use page.context.thread instead of page.context.message. More details on that here: https://developer.khoros.com/khoroscommunitydevdocs/reference/page-1
You could also get the root/topic from the page.context.message by doing something like: page.context.message.discussion.topicMessage
Thanks AdamN - exactly what we were looking for. 🍻
