The ECM Repository/Library menu item is used to administer the properties of the storage structures of the connected ECM systems in Microsoft Dynamics 365 Business Central.
The structure is not created manually but automatically transferred to Microsoft Dynamics 365 Business Central and supported by the system via the Import ECM structure action in the ECM server list and on the card of a configured ECM server. For example, for a Microsoft SharePoint site the libraries, content types and metadata fields created there are read from Microsoft SharePoint and stored in Microsoft Dynamics 365 Business Central tables.
The Import ECM structure action is typically used once, when an ECM stem is initially configured. It causes the entire structure of the ECM system to be duplicated to Microsoft Dynamics 365 Business Central. Following this, the structure can be checked and administered under ECM Repository/Library List.
However, configuration changes are not transferred back to the ECM system. The library and storage structure duplicated in Microsoft Dynamics 365 Business Central is only the basis for the mapping in Document Definitions.
Once you select an ECM structure, you should preferably retain it permanently. Reimporting the structure will only be required when new libraries, archives, and fields have been added to the existing ECM structure on the ECM system side.
For a partial update of storage structures, the ECM Repository/Library overview action can be used to open the list of the defined storages for the selected ECM server:
The Update metadata fields action allows you to update subsets without having to reimport the entire structure.
If the repository structure has been read in correctly, it should not be changed in Business Central. However, it may happen that certain configurations are changed at a later stage (e.g. a versioning) and these changes can be adjusted on the card page of the individual repositories.
When you mount the code unit ECM Structure Import Watchdog into the Microsoft Dynamics 365 Business Central task queue, you can automatically import the ECM structure through scheduler control. This may make sense in case of recurring modifications to the ECM system, e.g. when routinely creating new Microsoft SharePoint libraries.
Please note that when using the adaptive schema, a fixed schema is not used and therefore metadata fields are not displayed.