Expand my Community achievements bar.

Adobe Summit 2025: AEM Session Recordings Are Live! Missed a session or want to revisit your favorites? Watch the latest recordings now.
Watch Now!

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

Unlocking fields in LiveCycle

Avatar

Former Community Member
10/14/11 1:36:08 PM

I locked a field using the "lock" option from "edit", and now I need to unlock it. How do I do this?

I cannot send copies of the form out unfortunately.

Thank you to anyone who can help.

Views

2.4K

Replies

2

Total Likes

Translate
Translate
1 Accepted Solution

Avatar

Correct answer by
Former Community Member
10/14/11 4:16:27 PM

Lock acts like a toggle. Lock twice to unlock.

Steve

View solution in original post

Views

854

Replies

0

Total Likes

Translate
Translate
Jump to reply
2 Replies

Avatar

Correct answer by
Former Community Member
10/14/11 4:16:27 PM

Lock acts like a toggle. Lock twice to unlock.

Steve

Views

855

Replies

0

Total Likes

Translate
Translate
Jump to reply

Avatar

Former Community Member
10/21/11 11:28:43 AM

Excellent, thank you.

Views

914

Replies

0

Total Likes

Translate
Translate
Related Conversations
My data source works in Preview PDF mode but not when I generate the form Solved

Views

2.8K

Likes

0

Replies

2
Floating field with pagenumbers in a fragment is messing up when used in masterpages Solved

Views

1.6K

Likes

0

Replies

2
Change colons to periods in date/time field Solved

Views

1.2K

Likes

0

Replies

2
Decimal field: Sign in front of a positive amount? Solved

Views

1.1K

Likes

0

Replies

2
I want to create a field that includes information from 2 other fields Solved

Views

1.8K

Likes

0

Replies

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