Working with Class Tables¶
Overview¶
The Class tables refer to all the documents and other objects in the vault such as customers, customer documents, contacts etc. Any class as defined in the M-Files vault is a class table.
The class tables are not automatically created as the assumption is that an application or use case for the connection may only use a sub section of all the classes in the vault. A listing of all the classes is in MFClass.
Class tables can therefore be created on demand, updated in SQL and synchronized with M-Files either in batch mode or in transaction mode.
This section consolidates and deepens all guidance on class tables: preparation, synchronization, update methods, performance, operational patterns, and troubleshooting. It cross‑links existing blogs, example scripts, and procedure/function references so that the older scattered material can later be retired or folded in.
Scope¶
Preparing and validating class tables before large scale data exchange.
Choosing between full, selective, incremental, or property‑scoped sync.
Update strategies (batch, transaction mode, item-by-item, workflow/state sensitive).
Handling schema drift, new properties, lookups, multi‑value properties, aliases.
Performance tuning and safe scaling patterns.
Operational monitoring (ProcessBatch, logging, reconciliation).