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

link form page field to master page field

Avatar

Former Community Member

I have a word document converted to an Acrobat form. I have started to edit it in Live Cycle and want a field in the form page to link to a field in the master page. I have set the field up to work in the form page. However, as soon as I cut and paste the field (calculated) into the master, I get "Script failed (language is form calc..)" and "accessor TextField1.rawValue is unknown" errors. Is there any reason and fix for this issue?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Thanks for your help Srini. I found that naming the two fields the same and using the global option for the field worked

View solution in original post

2 Replies

Avatar

Level 10

Try placing the code in the Master page, rather than the form field.

Thanks

Srini

Avatar

Correct answer by
Former Community Member

Thanks for your help Srini. I found that naming the two fields the same and using the global option for the field worked

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