Object deactivation and caching about twenty HOT 2 CLOSED

To address the object deactivation and caching issue, ensure that after deactivating an object in SettingsObjectEdit.tsx via handleDisable, you also update the Apollo cache to reflect this change. Use useDeleteRecordFromCache from useDeleteRecordFromCache.ts to remove the deactivated object from the cache. If the object's data is still appearing, it might be due to stale cache entries. Implement a cache update in handleDisable by invoking deleteRecordFromCache with the appropriate parameters, including the object's metadata and ID. This ensures the cache is in sync with the current state of the object post-deactivation.

References

/packages/twenty-front/src/pages/settings/data-model/SettingsObjectEdit.tsx
/packages/twenty-front/src/modules/object-record/cache/hooks/useDeleteRecordFromCache.ts
/packages/twenty-front/src/modules/object-record/cache/utils/deleteRecordFromCache.ts
/packages/twenty-server/src/engine/api/rest/metadata-rest.service.ts
/packages/twenty-server/src/engine/metadata-modules/object-metadata/object-metadata.resolver.ts
/packages/twenty-server/src/engine/metadata-modules/object-metadata/object-metadata.service.ts
/packages/twenty-server/src/workspace/workspace-sync-metadata/factories/standard-relation.factory.ts
/packages/twenty-front/src/modules/views/hooks/internal/usePersistViewFilterRecords.ts
/packages/twenty-front/src/modules/views/hooks/internal/usePersistViewSortRecords.ts
/packages/twenty-front/src/modules/object-record/hooks/useDeleteOneRecord.ts
/packages/twenty-front/src/modules/object-record/hooks/useDeleteManyRecords.ts

Ask Greptile

from twenty.

This was fixed in #5316 which we need to rollout

from twenty.