{"id":89755,"date":"2025-06-03T13:16:26","date_gmt":"2025-06-03T12:16:26","guid":{"rendered":"https:\/\/churchtools.academy\/help\/non-knowledgebase\/uncategorized\/how-do-i-define-a-fallback-behavior\/"},"modified":"2026-08-25T12:46:54","modified_gmt":"2026-08-25T11:46:54","password":"","slug":"how-to-define-a-fallback-behavior","status":"publish","type":"docs","link":"https:\/\/staging.churchtools.academy\/en\/help\/churchtools-modules\/configure-connections\/how-to-define-a-fallback-behavior\/","title":{"rendered":"How to define a fallback behavior?"},"content":{"rendered":"\n

To enable data synchronization between two systems, the properties of the data must be linked so that ChurchTools knows which property in ChurchTools corresponds to which property in the external system and can be synchronized. They are linked into what are called property pairs<\/em>. The property pairs always apply to the entire connection. <\/p>\n\n\n\n

Some of these properties have values<\/em> that must also be linked to one another; for example, the ” gender<\/em> ” property has the values ” unknown<\/em>,” ” male<\/em>,” ” female<\/em>,” and possibly ” diverse<\/em>.” <\/p>\n\n\n\n

If not all values in a property pair are linked\u2014that is, if the link is incomplete\u2014this will prevent the execution of all sync jobs for which you have selected that property pair. <\/p>\n\n\n\n

To prevent this, you can define a fallback behavior<\/strong> for the relevant values. This allows you, for example, to synchronize the data first and then review the data assigned here in ChurchTools later to ensure it is correctly mapped. In this article, we\u2019ll show you how to define a fallback behavior. <\/p>\n\n\n\n