Preparing Class Tables

Goals

  • Ensure structural fidelity (all expected properties exist).

  • Establish consistent aliasing and lookup integrity.

  • Validate inclusion flags (IncludeInApp) before large batch operations.

Baseline Steps

-- 1. Synchronize structural metadata
EXEC dbo.spMFSynchronizeMetadata;

-- 2. Sync classes and properties explicitly if doing selective builds
EXEC dbo.spMFSynchronizeClasses;
EXEC dbo.spMFSynchronizeProperties;

-- 3. Pull specific metadata slices (e.g. value lists only)
EXEC dbo.spMFSynchronizeSpecificMetadata
     @SyncScope = N'ValueListItems';

Structural Verification

Use:
- spMFClassTableColumns
- spMFClassTableStats

Checklist

  • All required property columns exist (no stale / orphan columns).

  • Multi-value lookup expansion columns follow naming conventions.

  • Aliases synchronized (spMFAliasesUpsert).

  • Unique indexes applied if required (spMFSetUniqueIndexes).

Common Adjustments

Computed or staging columns (NOT pushed back to M-Files) can be prefixed (e.g. X_ or Stg_) to distinguish from authoritative M-Files property columns.

Caution

Do not manually rename native property columns—use synchronization + alias routines so internal mapping stays coherent.