I am creating an ECMA2 MA.
I have a couple of metaverse attributes, that I use ONLY when exporting - and that I cannot read back in an import, because they are not stored anywhere.
So the export works fine, but when I then try to Import, I get "exported-change-not-reimported" errors.
How can I avoid that?
One workaround is to define a constant import for an export-only attribute. This will not get rid of the "exported-change-not-reimported" errors on first import, but on subsequent export/import cycles, the constant value will have taken over, and I will not get the error again. Feels like a dirty hack though, since I still get the error first time around.
Another workaround could be to store the export-only values in a file or something, so I can import them again, but that seems like a lot of trouble for no value - and just another dirty hack.
If anybody is wondering "why would you export something, that you cannot import again":
An example is that on export I supply a geographic identifier, to determine which mailstore a new shared mailbox (exchange) should be created in. That geographic id is never stored anywhere, as it is only used temporarily.
---Sig---