SoftDelete issue in Custom object while migrating
@charles @thomast We created two custom objects in v0.23 and then migrated the database to v0.24 using the yarn command:prod upgrade-0.24 command. After the migration, the isSoftDeletable value is correctly set to true or false for both standard objects and newly created custom objects. However, for the custom objects created in v0.23, the isSoftDeletable field is returning NULL.
6 Replies
@Weiko
Hi @anjali This issue has been fixed in the v0.24.1, can you upgrade and run
upgrade-0.24:set-custom-object-is-soft-deletable ?Hello @Weiko , I am Anjal's colleague.
I ran the command yarn database:migrate:prod, and after executing it, the isSoftDeletable flag in objectMetadata was set to [NULL] for all objects. Then, I ran yarn command:prod upgrade-0.24, which updated the isSoftDeletable flag to true/false for all objects, except for custom objects that were already created in the previous version.
Yes, that's expected. As I said above please try the command upgrade-0.24:set-custom-object-is-soft-deletable instead
@Weiko I ran the following commands:
-
-
-
However, custom objects created in the previous version still have the
-
yarn database:migrate:prod-
yarn command:prod upgrade-0.24-
yarn command:prod upgrade-0.24:set-custom-object-is-soft-deletableHowever, custom objects created in the previous version still have the
isSoftDeletable flag set to [NULL], while other objects have the correct true/false values.
Am I missing any steps while migrating or any changes in the command sequence?
According to the update criteria, objects with the following conditions should be updated:
-
-
However, in the database, the
-
isCustom: true-
isSoftDeletable: falseHowever, in the database, the
isSoftDeletable flag for custom objects is [NULL]. Wouldn't this prevent them from being included in the update?