nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Capturing extended attributes for Pages in a SPAR

System

I observed that basic page attributes like Name, Location, Dependent URI’s etc are getting migrated using a SPAR for cross environment migration of pages

However, tagged metadata attributes and Livesite IDs are not getting migrated.

These attributes need to be migrated manually by writing them down manually for each page in a file called “eamanifest.xml”. This file is bundled in the spar within the meta-inf folder.

I wish to know if there is any way to overcome this manual overkill. Please suggest.

Find more posts tagged with

Comments

Migrateduser

Repost: Any ideas on this please?

Migrateduser

Repost: Any ideas on this please?

vpatel

IDs and some of other metadata usually get generated on the fly to avoid conflicts. The answer to your requirement today is eamanifest.xml. I've seen a few companies write a "script" that will extract all EAs for relevant files and create this eamanifest.xml file automatically. You could probably write that script relatively quickly if this is something that you do all the time.