Expand my Community achievements bar.

SOLVED

click a button to change the Master Page

Avatar

Former Community Member

Hi everybody,

I have a LiveCycle Designer question…

Is it possible to have a button onclick event to change the Pagination “Place” property of a subform?  I would like to change the Master Page that a subform is placed on using a script on an onclick event. I’m not sure if this is possible… wondering if you knew a way…

Thanks a lot.

Jing

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi Bruce,

Thanks a lot for your help!

I think I fixed the issue…


The form has the script set to the click event of buttons:
Page3["#breakBefore"].targetType = "pageArea"; 
Page3["#breakBefore"].target = "MasterPage4";   
xfa.layout.relayout();


Thanks

JIng

View solution in original post

3 Replies

Avatar

Level 10

Hi Jing,

I don't think it is easy, here is a sample that allows you to choose the page size and orientation (which are different master pages), Adobe LiveCycle Designer Cookbooks by BR001: Season Planner (or Year Planner) PDF Template

It effectively defines the form against each master page and recalculates the widths and heights when the page selected is made, but I don't know of another way.

Regards

Bruce


Avatar

Former Community Member

Hi Bruce,

Thanks for your kind attention,but I cannot connect to the web site you provided.


Regards


Jing

Avatar

Correct answer by
Former Community Member

Hi Bruce,

Thanks a lot for your help!

I think I fixed the issue…


The form has the script set to the click event of buttons:
Page3["#breakBefore"].targetType = "pageArea"; 
Page3["#breakBefore"].target = "MasterPage4";   
xfa.layout.relayout();


Thanks

JIng

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