It would be great if related entities were recorded in history entries. For example, when a room or resource is removed from a reservation, a history entry is added that records the room or resource in the ValueName column. This is fine for a human visually scanning later, but if there's a desire to do reporting or take action on deleted resources, we have to fall back to matching on entity name.
The history table has RelatedEntityTypeId and RelatedEntityId columns that would be perfect for capturing this data. In the scenario of a room or resource being removed from the reservation, the entity id for either resource or location could be recorded along with the entity id.
It would be great if related entities were recorded in history entries. For example, when a room or resource is removed from a reservation, a history entry is added that records the room or resource in the
ValueNamecolumn. This is fine for a human visually scanning later, but if there's a desire to do reporting or take action on deleted resources, we have to fall back to matching on entity name.The history table has
RelatedEntityTypeIdandRelatedEntityIdcolumns that would be perfect for capturing this data. In the scenario of a room or resource being removed from the reservation, the entity id for either resource or location could be recorded along with the entity id.