Skip to main content
Skip table of contents

Troubleshooting the Macro Migration Assistant

Broken Legacy Table Enhancer Macros

Converting a page to the new editor can break legacy Table Enhancer macros on that page. This typically happens because the legacy macro was wrapped inside another macro. The content of broken Table Enhancer macros is no longer accessible. This makes it impossible to migrate broken legacy macro without a manual intervention. Learn how to fix broken legacy Table Enhancer macros.

The Macro Migration Assistant will notify you if it encounters a page containing a broken macro during the macro migration process. It will also insert a section message at the top of the affected page informing users about the presence of broken legacy macros on the page.

broken_macros_flag.png

The assistant will notify you if it encounters a broken macro.

page_with_a_broken_macro.png

The Macro Migration Assistant inserts a section message at the top of pages containing broken legacy macros.

How the Macro Migration Assistant Performs the Macro Migration

The Macro Migration Assistant performs the following steps to migrate all legacy Table Enhancer macros contained in a given page:

  1. Extract all content wrapped in legacy Table Enhancer macros to the ambient page

  2. Wrap all tables extracted in the previous step in expand macros

  3. Add a Table Enhancer Cloud macro above each expand created in the previous step

  4. Copy the macro configuration from the legacy macros to the new macros

  5. Delete all legacy Table Enhancer macros on the page

  6. Issue a page update

This process only migrates Table Enhancer macros themselves. You might still have to migrate some table content.

image-20240212-130127.png

A page containing a legacy Table Enhancer macro.

image-20240212-125844.png

The same page after a macro migration was triggered through the Macro Migration Assistant.

image-20240212-125912.png

The page history after a macro migration was triggered through the Macro Migration Assistant.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.