Expand my Community achievements bar.

SOLVED

The form readOnly access property is not retained after saving it.

Avatar

Level 1

Hi all,

I had a form that I created in Acrobat and further added some features using LiveCycle. Pressing a button on the form was making it readOnly.

By saving it in Acrobat with proper rights, in Reader, I was able to fill the form, make it readOnly and save it.

This was working fine until I decided to make some modification to it in LiveCycle. I did that and again saved in Acrobat with proper rights.

Now in Reader, I'm able to fill it, make it readOnly and save it but next time that I open the form in the Reader, it's not readOnly anymore.

As you see it was possible first and then got broken. I have no clue why the form does not save the readOnly access property.

It becomes readOnly when I press the button and stays like that until I close it, though.

Any help would be highly appreciated,

Cheers,

Kamil

Acrobat Pro X

LiveCycle ES2

Win XP SP3

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Open the form in Designer, under the File/Form Properties/Defaults menu option make sure the preserve scripting changes radio button is set to Automatic.

Save the file and try it again.

Paul

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Open the form in Designer, under the File/Form Properties/Defaults menu option make sure the preserve scripting changes radio button is set to Automatic.

Save the file and try it again.

Paul

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