Custom Integration drops all fields

Get Help
1

What is the specific mechanism that makes Custom Integrations reset all of their fields?

I’ve been working on an integration with lots of fields and as I refactor, the integration periodically chooses to set every optional field to ‘Skip’, even when I’m not making schema changes. This takes a ton of time to fix unless I just delete the integration and reinstall, but I know this isn’t great either as I can eventually hit the schema limit and no longer be able to make fields.

I’d love to know how to avoid this problem.

2

Looks like a bug, we will check asap

3

Hello, @Tommy_Hedley

Could you please double check that you didn’t change ids of fields or type ids in synchronisation schema? The described behaviour happens when the schema/fields are changed.

Thanks.

4

Ah, a bit embarrassing on my part :sweat_smile: . I was doing some AI refactoring and it changed the case on a single letter on a field replicated on all dbs. I totally missed it on my first pass. It did still set every field for every db to skip, which seems a bit unnecessary, but it was due to a schema change.