You can create a new field.
Then execute "Old field":="New field" in OnValidate() trigger of this new field, so that the value will be saved in "old field", and its OnValidate Trigger will not be executed.
PS: Dynamics 365 Business Central: The difference between Record.Validate() Method and assignment statement
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.