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

Adaptive form validation (server side)

Avatar

Former Community Member

Hi.

We are having the same issue as noted here:

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/aem-forms.topic.forum__...

So trying to get errors back to the client from the server, to report to client.

We tried using post.POST.jsp with the solution posted in the above post, but we are getting already committed errors. 

See "21.12.2016 15:45:28.885" in the attached log.

Suggestions?

Joel

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Switched to a form containing an adaptive form, and controlling from client lib/guideBridge via an external button I added manually.

Making progress now.

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Switched to a form containing an adaptive form, and controlling from client lib/guideBridge via an external button I added manually.

Making progress now.

Avatar

Level 3

Hi Joel,

Apologies for the delay. Let me know if you face any further issues with your custom implementation. 

Thanks,

Rishi

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