Versions Compared

Version Old Version 22 New Version 23
Changes made by

Matthew Wagner

Matthew Wagner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When you switch from one layout to another, XperienCentral maps the fields from the original layout to the one being switched to in the most logical way possible. Because layouts can vary widely, switching from one layout to another can correspondingly have widely varied effects. Depending on the circumstances under which you switch to another layout and what you've already done in the layout you're switching from, there are a number of things to consider. For example, if you have already filled content into one or more fields and/or if there exist prefilled fields at the time you switch to another layout, you could lose content.


Tip
  • For best results, switch first to the other layout in order to determine whether that leads to undesired results. If it does,
do not save the content item and immediately
  • switch back immediately to the original layout in order to
preserve
  • restore the data in all the filled in/prefilled fields you have modified.
  • When switching between layouts, do not save the content item until you are satisfied with the results. A save action makes it impossible to switch back to the original layout while at the same time restoring all data.

The following table explains how XperienCentral handles a layout switch and how fields and loops from one layout are mapped to another (or not). The mapping logic takes into account what is available in the structure of the layout being switched to and then applies the rules described below.

...