Hi @JMoleroAlonso,
As I had mentioned in previous messages, you cannot set the field as “unique value” if there is a change that field values will be the same.
To illustrate, this is NOT unique because values for “subscription__monthly” are identical:
{ ‘id’:‘record1’, ‘subscription__monthly’: ''}
{ ‘id’:‘record2’, ‘subscription__monthly’: ''}
To resolve this issue you have two options:
Option A: Change your unique value to a field that will ALWAYS have unique values, such as “id” or “email” - this will allow passing null values in “subscription__monthly” field
Option B: If you are required to have “subscription__monthly” as the unique value, make sure your “subscription__monthly” field always has unique values. Example of option B:
{ ‘id’:‘record1’, ‘subscription__monthly’: 'null_1'}
{ ‘id’:‘record2’, ‘subscription__monthly’: 'null_2'}