Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.
SOLVED

How do I keep instances added in order after saving?

Avatar

Level 2

Ok so I've come across a problem in my pdf form. I got the add instance button to work and with some help from the boards here I managed to get it to add the pages in the right order. However, once I've added some pages and save my work, if I open the file again the pages added are no longer in the order they're supposed to be in. I've included the pdf so you can see what I mean. The pdf starts out as 4 pages with the middle two being the front and back of whats called a stat card. These two pages must be together to enable printing the form as a front and back page. But once the file has been saved after you've added another set of stat cards then it regroups the pages as front, front, front, back, back, back. I cannot let this remain this way if it's going to be at all useful to as many people as possible. Please tell me what's wrong with it and why it's doing this.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

You have an object called fullform that you have defined as a subform set. Change this to a subform and it should work fine.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

You have an object called fullform that you have defined as a subform set. Change this to a subform and it should work fine.

Paul

Avatar

Level 2

Thanks Paul that did the trick. You're a miracle worker for sure.

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