Master Page Map - order of application (FM2019

[QuintinSeegers]

I can't seem to find any specific clarification on the Help file. Can someone clarify the order in which the Master Page Mapping is applied?

In my Master Page Maps I have two rules that changes the master pages based on two specific elements:

• Element A changes the master pages to ones without headers/footers
• Element B changes the master pages to ones that have a landscape layout

If Element A and Element B appear on the same page, regardless which one appears first on the page, the Mapping for Element A is applied. If only one of these elements appear on the page, the correct master pages are applied.

Is the mapping applied on a first in the list rule? I.e. for each Master Page Map rule, the page is scanned, and if the Element appears, the rule is applied and no further rules are checked?

[Barb Binder · Accepted solution]

Hi Quintin:

Interesting question, and while I rely heavily on the feature, this is a situation I have not encountered IRL. It sounds like Fm is reading the first line of the master page mapping table, finding the specified paragraph style, assigning the master without the running head and moving on to the next page without ever considering the second option. Does changing the row order on the master page mapping table reference page make a difference?

What do you want Fm to do if it encounters the two paragraph styles on the same page: apply the page without the running heads, or apply the landscape master? Or does it vary?

Is there a way to ensure that only one of the two styles appears on a given page, so that it always maps the correct master?

~Barb

[QuintinSeegers]

Hi Barb,

In our case it is unusual that we would have conflicting master pages. In this instance it turned out that the wrong Element was being used on the page, causing the perceived conflict. Once it was changed to the correct Element, the behaviour was as expected.

I wasn't so much looking for a solution to a self-caused scenario, as much as confirming my interpretation of how mapping rules are applied, was correct. It also explains other unexpected behaviour we experienced in the past with master page mappings.

Thanks,

Quintin

[Bob_Niland]

    My impression has always been that AMP stops searching the UnstructMasterPageMaps Table when it gets the first match. This is normally not an issue for most users & documents, and I suspect that most people do what I do, which is have the Paragraph Tag Name column in alphabetic order. It could of course be in priority order if needed.

    And on the subject of AMP, unless it's been enhanced, text in Body Tables is ignored for mapping purposes. The Master Page used for the Table is determined by the L/R MP or Range Indicator most recent MP assignment triggered by something else before the table.