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

deleted rows are resurrected when the form is reopened

Avatar

Former Community Member

I have a form that allows users to add and delete rows om a table.  This works fine while the user is viewing and editing the form, but when the form is saved and then reopened, previously deleted rows reappear.  How can I make sure my deleted rows stay deleted?

The script for click for the delete button reads:

this.parent.instanceManager.removeInstance(this.parent.index);

Thank you for any insight into what is causing the deleted rows to reappear when the document is reopened.

Noam

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

This issue was resolved by associating a schema with the form which allowed the form to save state.

View solution in original post

2 Replies

Avatar

Level 1

Is it a table? or just a repeating section? I am not sure if it makes a difference with tables, but on the repeating subforms there is a setting for the default number of instances - maybe this is causing the behavior? Otherwise, I don't know...back in previous versions I used xfa.form.remerge() after any instance manipulation - but I don't anymore.

Good luck.

Avatar

Correct answer by
Former Community Member

This issue was resolved by associating a schema with the form which allowed the form to save state.

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