Hi Ian, recently I developed a work around for this issue as a customer wanted to retain data from entities even after an element is removed or after the entities are removed from the table they resided in. What I did was leverage an automation script to query the cassandra database. In order to do that you would need query it with the entity’s partitioning key which is a combination of (dma id, element id, parameter id of the value you want, primary key, and window). More info about querying cassandra is found here https://docs.dataminer.services/develop/devguide/Connector/AdvancedDataMinerDataPersistenceNoSqlCassandra.html#data-table . In order to keep this data so that when the element is removed or entity is deleted I added logic to export a file with these values needed for the partition so you can leverage the info after an element is deleted. If you have questions on how to implement this or if it seems relevant to your problem feel free to reach out to me on teams or via email.