When restoring a StorageSet from an SQL db storage location, the corresponding pointer is assigned to a new id, although the old id is still referenced in the storage.
This only happens when Datex.Runtime.OPTIONS.INDIRECT_REFERENCES is enabled. I don't think this is a general problem when indirect references are enabled, but this seems to be an edge case where it leads to problems.
Until this is not fixed, we cannot enable INDIRECT_REFERENCES per default.
When restoring a StorageSet from an SQL db storage location, the corresponding pointer is assigned to a new id, although the old id is still referenced in the storage. This only happens when
Datex.Runtime.OPTIONS.INDIRECT_REFERENCESis enabled. I don't think this is a general problem when indirect references are enabled, but this seems to be an edge case where it leads to problems.Until this is not fixed, we cannot enable
INDIRECT_REFERENCESper default.