change-management-and-vault-moves

Why synchronising the metadata

The vault structure is captured in metadata baseline tables such as classes and object types. Synchronizing the metadata updates the metadata structure of the specific vault into these inter-related tables. These tables are used by MFSQL Connector to process against a replica of the vault structure. Note the following special considerations. - Refer to Metadata Structure Tables for more details on the structure tables - All ValueListItems are contained in a single table. The column AppRef contains a unique reference that can be used in applications to access a ValuelistItem without reference to the valuelist. The AppRef consists of the Valuelist MFID and the Item MFID and is automatically created by the Connector. - The spMFCreateLookupView procedure can be used to create a view for a specific valuelist to be used in applications. - The columns MFID and Name of the ValuelistItems in the MFValuelistItems table are not unique as this table includes all valuelist items across all valuelists. - After deployment of the Connector, the metadata of the vault are added to the baseline metadata tables by synchronising the metadata using the spMFSynchronizeMetadata procedure. When changes are made to the metadata structure in M-Files using the administrator the same procedure can be used to refresh the metadata. Note that metadata is not automatically refreshed. It is refreshed on demand. - Metadata maintenance - The spMFSynchronizeSpecificMetadata stored procedure can be used to refresh a specific type of metadata such as valueslist items or states.