How publishing works
-
When you publish a version from Mavim Manager to the Portal, it does not automatically appear in SharePoint.
-
To make the version available in SharePoint, you must publish it to the taxonomy in your SharePoint environment using the Office 365 tab in the Portal.
Maintaining connections between versions
-
After publishing a version to SharePoint taxonomy, you can create links to that publication.
-
Example: If you publish Processes Final 7011, relate it once to the taxonomy.
-
When you later publish Processes Final 7012 to the Portal, the existing relations will automatically be applied to the same elements in this new version — even if you don’t publish it to SharePoint again.
-
If the new version contains additional elements that need connections, you must publish that version (7012) to SharePoint taxonomy.
When relations are not inherited
-
If you create a completely new version definition in Mavim Manager (for example, moving from version series 7xxx to 8xxx), this is treated as a new publication.
-
In that case, links from the older version (7011) will not transfer to the new one (8001). You must set the relations again.
-
To avoid this, continue working within the same version series (7011 → 7012 → 7013, etc.).
Why more versions appear in SharePoint
-
When you delete a version from the Portal, it is not automatically removed from SharePoint.
-
Example: If you published and linked Processes Final 7011 in SharePoint taxonomy and later delete it from the Portal, the taxonomy structure remains in SharePoint.
-
This explains why SharePoint may show more versions than the Portal.
You must manually maintain and clean up the SharePoint taxonomy.
Notes
-
Always publish to SharePoint taxonomy at least once per version series.
-
Continue using the same version definition to preserve links across publications.
-
Clean up SharePoint taxonomy regularly to keep versions aligned.