Keep module connections stable when databases or interfaces change

You need to remap fields when the connection between a module and a target database can no longer rely on the previous field alignment.

Common situations include:

• Reconnecting a module
  If a module connection was disconnected or deleted and later added again, fields must be mapped again to align source and target data.
• Applying interface updates
  When a module provider changes the exposed interface (for example, by adding or removing fields), consumers may need to remap fields before syncing resumes.
• Changing fields in the source database
  If the provider changes fields within the same table but keeps the interface fields stable, remapping ensures the interface still points to the correct source fields.
• Changing fields in the target database
  If a consumer restructures fields in the target database, remapping lets the connection continue without changing the interface contract.

Remapping works at the interface level: interface fields remain stable through their IDs, while source and target fields can evolve independently.

Related articles

• Mapping fields in modules