After migration, users observe that tabbed tables no longer appear as tabs. Instead, all tabbed panels are flattened into individual simple tables or only the content from the last selected tab is migrated, leading to loss of the intended tab structure and potential missing content.
Known Limitation in MNSP Documentation: The migration engine treats tabbed tables as separate tables rather than maintaining the tab interface. Each tab is processed independently, producing individual tables instead of a tab set.
Last-Active Tab Storage Behavior: The system stores and migrates only the content from the tab that was active when the database was last closed. This is how the "last active" view is persisted in the backend and is operating as designed.
Split Tabs into Separate Tables
Before migration, replace each tabbed table with its own standard table. For example, if you have five tabs, create five standalone tables in your source documentation.
Rerun the migration process; each table will transfer exactly as intended.
Ensure Correct Tab Selection (Workaround)
If splitting tabs is not feasible, manually select the desired tab just before closing the database.
This ensures that the content of the chosen tab is the one that gets migrated, as the system migrates based on the last active view.
