Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Is there another way to get the doc object other than event.target

Avatar

Former Community Member

I have a situation where event.target is returning undefined.

I have JavaScript in the preSubmit event that was not firing when clicking the Save button in Workspace. I tracked down that this button through the Form Bridge calls saveXML. The code I need run alters the XML so I still need it run before saving. I added a call to execute the preSubmit event prior to the saveXML line. My code failed as I found out because when using event.target in the preSubmit event, it is undefined when called from teh Form Bridge code.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

I noticed the form bridge code itself used event.target. I am gathering from the comments that the event object is changed by this code so the target child is no longer there. I created a variable at the top and set it to event.target before where I believe was going to be changed. I then used that variable and it solved my problem.

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

I noticed the form bridge code itself used event.target. I am gathering from the comments that the event object is changed by this code so the target child is no longer there. I created a variable at the top and set it to event.target before where I believe was going to be changed. I then used that variable and it solved my problem.

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] ----