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

Dynamic table generation

Avatar

Level 2

Hi everybody !

I'm using Adobe LiveCycle Designer ES free trial.

I have a set of data and two pdf. The first is a pdf i got on the web, which was created with Adobe LiveCycle Designer ES full version.

The second is the one i created with the trial version.

I'm trying to display several data like this:

    <history>
        <date>08/05/2009</date>
        <doc>doc</doc>
        <desc>desc</desc>
    </history>

    <history>
         <date>09/05/2009</date>
         <doc>doc</doc>
         <desc>desc</desc>
     </history>

     ...


With the first pdf it works fine. All the data are displayed.

But only one data is displayed with mine.

I checked all the options (like binding) and there are all the same on the two pdf.

So is there a limitation on the trial version with repeating data ??

Thanks

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

No there are no limitations in the trial version, but the one you got from the web is probably saved as a dynamic PDF and yours is probably not saved that way.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

No there are no limitations in the trial version, but the one you got from the web is probably saved as a dynamic PDF and yours is probably not saved that way.

Paul

Avatar

Level 2

Thanks. It is exactly what i was looking for.

Guillaume

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