There are many business uses cases where dataflows are used to upload data from legacy systems into Dataverse. One common use case is uploading user lists or product lists. These lists often contain active records only, the inactive records having been removed from the legacy systems. For example, employees who have left a company may no longer be in the user list from the legacy system.
When loading data into Dataverse with a dataflow, there currently is an option to "Delete rows that no longer exist in the query output". This is practical, but there are many use cases where deleting these rows (records) is not the best option. It would be better to have a new option to "Set the status of rows that no longer exist in the query output to Inactive". (see figure below)
That way, it would be easy to track "fresh" data from legacy systems, without losing old data which may still be of use for analytical and historical purposes.