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

Associating Form Design

Avatar

Level 1

Hi everyone.

I'm having troubles with this functionality in the detailed view of a space.

I always get:

'Failed to retrieve form design fields from the document.'

I´ve tried saving the form design on LiveCycle Designer in every possible way (Static PDF, Dynamic PDF, XDP, etc)

The worse thing is that I haven´t been able to find good documentation on this item.

Thanks a lot in advance for your help.

Best regards,

Hector Castro M.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

The form can be either an XDP or a PDF but the form must have a schema associated with it for this feature to work. You must also choose the embed the schema option in the Form Properties for the fields to be extracted. I have included a sample form that has the schema embedded in it in boith XDP and PDF formats.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

The form can be either an XDP or a PDF but the form must have a schema associated with it for this feature to work. You must also choose the embed the schema option in the Form Properties for the fields to be extracted. I have included a sample form that has the schema embedded in it in boith XDP and PDF formats.

Paul

Avatar

Level 1

Thanks Paul,

It worked fine.

Regards,

Hector.

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