Hello,
Does anyone know of a way of reinitializing or revalidating programmatically the Configuration section of a vault application inside of M-Files Admin when MFIdentifier-type configuration settings are resolved within the vault app? Currently, the errors and warnings that alert the user that the aliases set in this settings cannot be found only disappear if I refresh the entire vault node in the left-hand tree. To be clear, these are the errors that I wish to make go away:
More context:
I have a vault application that contains some installation tasks as well as user-initiated (from Admin) content import tasks:
1. Upon installation the app sets a few configuration settings of type MFIdentifier in NVS to a default value (aliases for two classes).
2. In the configuration section, has a command that kicks off a content import that contains the two classes referenced in the configuration. After the content import is finished, I run VaultApplicationBase.ReinitializeMetadataStructureCache(PermanentVault), then check if the two MFIdentifier settings are resolved (Configuration.<SettingName>.IsResolved), and if not, resolve them by calling Configuration.<SettingName>.Resolve(transactionVault, typeof(MFilesAPI.ObjectClass), true).
As it currently stands, the configured MFIdentifier settings are resolved through this process, and I can use them in my vault application without error. However, the user who is installing and performing initial setup of the vault application will be working primarily within M-Files Admin and after running the content import may be alarmed by the red errors that say that the two default MFidentifier values cannot be found despite them already being resolved within the vault application. I have tried calling ClientOperations.UpdateDomain() and ClientOperations.RevalidateDomain() after the import is completed within the command but to no avail.
Thanks in advance for any ideas!
