topic Re: MVO export>import to another project's view settings? in Modeling

MVO export>import to another project's view settings?

gaba — Mon, 22 Dec 2025 11:29:17 GMT

How can I import MVO settings (e.g., "my mvo name") into another project so that they end up in the MVO settings with the same name as "my mvo name" (i.e., they don't get duplicated as "my mvo name(1)"). Meaning, the imported "my mvo name" will replace the existing "my mvo name" and not lose its connection to the view settings?!

Maybe I should change something (Guid?) in the XML of the exported MVO before importing?

... <LibraryGlobal> <LibraryGlobalName>LibraryGlobals13</LibraryGlobalName> <LibraryGlobalGuid>9137124A-DDF2-4A06-A532-5FC0CE873258</LibraryGlobalGuid> <LibraryGlobalSupersetGuid>00000000-0000-0000-0000-0000000000</LibraryGlobalSupersetGuid> ...

Operating system used: Windows

Re: MVO export>import to another project's view settings?

Laszlo Nagy — Mon, 22 Dec 2025 11:51:05 GMT

You can try exporting the MVO combination in question, open the XML and you will see its GUID. Then try to copy this GUID into the place of the GUID of the MVO you wish to import, and see if that produces the desired result.

Re: MVO export>import to another project's view settings?

gaba — Mon, 22 Dec 2025 12:14:30 GMT

Unfortunately, the same GUID doesn't help. After importing, I get a clone: "my mvo name (1)" If I delete "my mvo name" and then immediately change the name: "my mvo name (1)" > "my mvo name" the views won't switch to the new imported "my mvo name" settings; and the views simply indicate the absence of "my mvo name"; Manually switching the views to the imported "my mvo name" is a Sisyphean task.