Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Differentiating Between ITEM_RECEIVE Events

Avatar

Employee

When I connect to an existing CollectionNode the first thing it looks like it does is grabs all of the items on that node, so the ITEM_RECEIVE event fires and calls my callback function.

Is there any way to see whether that event came on the initial connection/syncronize event versus coming from something that happened after I connected?

Is an isSynchronized flag the best way to handle that?

=Ryan

ryan@adobe.com

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Yup, definitely filtering for collectionNode.isSynchronized is the best way to tell.

nigel

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Yup, definitely filtering for collectionNode.isSynchronized is the best way to tell.

nigel

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----