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

Getting XML from Adaptive form fragment submit

Avatar

Former Community Member

I am using AEM 6.2 on Windows 7. I have an adaptive form embedded on a plain page. I am validating/submitting the adaptive form using an external button and  GuideBridge. See (Fragment.txt) attached.

The adaptive form contains an adaptive form fragment.

"===================="

Plain Page

--AdaptiveForm ("Last Name")

----Adaptive Form Fragment ("Leader Name")

"===================="

 

The data in the fragment does not show up in the XML. (Data: Last Name: "last", Leader Name: "leader")

See "XML data received" log message.[0]. The problem here is the "Leader Name" does not show in the XML.

Any idea why? Am I using the wrong API to get the XML for the fragment?

Is guideBridge.getDataXML({ .... success : function (guideResultObject) {

console.log("XML data received" + guideResultObject.data);

not correct?

-Joel

[0]"============================"


XML data received<?xml version="1.0" encoding="UTF-8"?><afData>
  <afUnboundData>
    <data>
      <lastNameField>last</lastNameField>
    </data>
  </afUnboundData>

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Figured it out. I was using an XSD based form. Switched to a plain adaptive form and it's all working now.

-Joel

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Figured it out. I was using an XSD based form. Switched to a plain adaptive form and it's all working now.

-Joel

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