Instead of having to change the ID to another user, could you do the following:
- add a field to the DataEntity object named ODataPublishedChangedBy
- Add an on-commit event for DataEntity that retrieves the account of the current user and populates that field with the name of the current user
- Add a startup event that retrieves all DataEntities, loops through, retrieves the system.user from the ChangedBy association, and populate the ODataPublishedChangedBy. You can add error handling/conditional logic so that if you try to retrieve a system user that does not exist, it will skip and populate the value for ODataPublishedChangedBy with ‘empty’ or ‘deleted’ or something similar
I know this isn’t ideal, but this will allow you to remove the ‘changedby’ association from your OData published resource and still let you push the relevant data out in the OData feed. That way if another account gets deleted in the future, you won’t have to go through this trouble all over again.