I have a model with a simple field I created. In the next migration I wanted to make this field required, however the update was being rejected, even though I was passing a migration value.
When testing I noticed that I had to delete every entry and then I could update the field to be required.
In the UI this isn't an issue as it asks for a migration value. I assume there is some sort of ordering of mutations issue meaning that the migration is rejected?
e.g
model.addSimpleField({
apiId: 'label',
displayName: 'Label',
type: FieldType.String,
isLocalized: true
});on next run when content has been added (this fails)
model.updateSimpleField({
apiId: 'label',
migrationValue: 'test',
isRequired: true
});
I have a model with a simple field I created. In the next migration I wanted to make this field required, however the update was being rejected, even though I was passing a migration value.
When testing I noticed that I had to delete every entry and then I could update the field to be required.
In the UI this isn't an issue as it asks for a migration value. I assume there is some sort of ordering of mutations issue meaning that the migration is rejected?
e.g
on next run when content has been added (this fails)