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

Detect Form Changes

Avatar

Level 3

I have a submit button in a form and when the user clicks it, I want to check to see if they changed anything on the form. If they did, I will advise them to save the form before submitting.

How would I determine if anything changed?

Thanks for the suggestions....

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

There is a flag set by Acrobat that tells it when something has changed (so it knows to bring up the SaveAs dialog when you close the doc). You can check the status of this flag yourself.

event.target.dirty

It will return a true value if soemthing has changed and a false value if nothing has changed.

Paul

View solution in original post

3 Replies

Avatar

Correct answer by
Former Community Member

There is a flag set by Acrobat that tells it when something has changed (so it knows to bring up the SaveAs dialog when you close the doc). You can check the status of this flag yourself.

event.target.dirty

It will return a true value if soemthing has changed and a false value if nothing has changed.

Paul

Avatar

Level 3

Just learning.....

What does the syntax look like for this?

if event.target.dirty = .t.

{

     do something

{

Avatar

Former Community Member

If (event.target.dirty == true){

app.alert("You have made changes to your doc .....make sure you save");

}

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