Skip to main content
Inspiring
February 3, 2012
Answered

Losing Master Page Assignments After Page Layout Import

  • February 3, 2012
  • 1 reply
  • 833 views

I've got a book with about 40 chapters, and I'm changing the layout.  I update the master pages in Chapter 1, and then use Import formats to import the master pages to the other chapters.

However, when I go to the other chapters, the first pages lose their "first" page assignment, and just come up with a normal L/R assignment.

If I manually go to Master Page Usage, and change the first chapter page to "first" it works OK, but that's going to get a bit tedious for all these chapters.

Is there any way to keep the existing master page usage assignments when importing the page layout?

Thanks!

John

    This topic has been closed for replies.
    Correct answer JohnHuntington

    Aha, interesting.  Of course when testing this this morning it didn't have that problem. 

    But your message prompted me to finally figure out that cryptic MasterPageMaps and I now have made a table like this, which seems to be doing the trick:

    Paragraph Tag NameRight-Handed Master Page (or Single-Sided Master Page)Left-Handed Master PageRange Indicator (Single, Span pages, Until changed)Comments
    ChapterTitleFirstSingleChapterTitle page to first master page

    Thanks as always for your speedy and helpful reply!

    John

    1 reply

    Bob_Niland
    Community Expert
    Community Expert
    February 3, 2012

    Is the Reference Page MasterPageMaps still intact after the import?

    Any changes to the mapping table?

    Any chance you are importing Reference Pages as well as Page Layouts?

    JohnHuntingtonAuthorCorrect answer
    Inspiring
    February 3, 2012

    Aha, interesting.  Of course when testing this this morning it didn't have that problem. 

    But your message prompted me to finally figure out that cryptic MasterPageMaps and I now have made a table like this, which seems to be doing the trick:

    Paragraph Tag NameRight-Handed Master Page (or Single-Sided Master Page)Left-Handed Master PageRange Indicator (Single, Span pages, Until changed)Comments
    ChapterTitleFirstSingleChapterTitle page to first master page

    Thanks as always for your speedy and helpful reply!

    John

    Bob_Niland
    Community Expert
    Community Expert
    February 3, 2012

    I presume that ChapterTitle is paginated to appear only At Top Of Right Page. if not, you may want to create a "First.Left" master page as well and not leave that "Left-Handed Master Page" column blank.

    Welcome to AMP

    That Reference Page table is what informs the Apply Master Pages (AMP) operation. Some random things to know about the mapping table:

    • Reference Page MasterPageMaps doesn't exist by default in a from-scratch document. Running an AMP for the first time throws a dialog and creates it. You can also import RPs from another document.
    • Paragraph Format names and Master page names must be exact (spelling, caps, punct. and probably no trailing blanks).
    • If an MP layout is named in the table, but doesn't exist, AMP throws an error even if that page is never mapped in that document.
    • If a Body page has paragraphs with conflicting MP mappings, the first encountered in the Flow prevails (apparently). This is either a benefit or a hazard, but now you know how it works.
    • Text on Master Pages is presumably ignored for AMP purposes (you'd sort of expect that).
    • What you might not expect is that Body tables (including titles and footnotes thereof) appear to be entirely ignored for AMP. If a table needs a special page layout, trigger it with the anchoring paragraph, and set the Range Indicator for the mapping to "Span pages". You will need to revert to Left/Right with some other paragraph following the table. I haven't tested text within anchored frame with AMP.
    • Running an AMP can easily cause repagination. I always run it separately, and before Update Book. Update Book (or Update References) can itself cause repagination.
    • The AMP option in the Update Book menu is unstable in FM7.1, so I never use it. I have often seen it generate incorrect page mappings. It appears* to cycle the process until no further pagination changes occur, but apparently there's a bug.  I have not tested FM9 to see if this is fixed.

    _______________

    * If the Update Book process detects an oscillation, it makes an assumption and quits. This scenario can arise when repag requires a re-AMP, and the re-AMP causes a contrary repag.