Clone Use Pre-populated fields

Problem/Motivation

I have a field in a content type that uses another field defined in the users profile to build a URL. So if "User1" creates a node it will pre-populate that field with https://website.com/User1URL.

But if another user, let's call them "Moderator2", who has access to clone the node instead of using the existing URL that was in the original node, it replaces it with https://website.com/Moderator2URL and has to be manually changed back to the information from the source node.

Proposed resolution

If a field that has a Entity Prepopulate formula defined, but the original node already has existing data, ignore the Entity Prepopulate entry and use the existing.

As an alternative, if the field is set to be excluded, then it should revert back to using the Prepopulate formula.