Is there a way to turn off the table in SQL Server being create with NOT NULL when the field is Auto Number in Salesforce?
We never went back to set default value in SF.
Skyvia creates target tables according to the definition of source objects (with the same names, data types, and constraints) and there is no way to change this behavior in the package settings. The only way is to remove the not-null constraints manually directly in your database.
Well in Salesforce you can set the field to be Auto Number, and it can have duplicate IDs in the field PRior to when you set it up in Salesforce. So even though you might think this is an error, Salesforce is OKAY with it.
You should add an option to NOT create NOT NULL, or unique key constraints, or give us an option to change it on Replication to SQL SErver. Your competitors allow it.
Thank you for your reply.
Skyvia creates a target database table according to the current source schema and if the field cannot be null in the source (e.g. auto-number), the same constraint will be added to the target table.
We have a feature request for adding options for target schema creation. We don't have any ETA, however, we will definitely inform you when it is implemented.