On June 17, we will deprecate the following settings in Master Data v1: Calculated Field and the Change field value trigger action.

Instead of using these settings, we recommend one of the following alternatives to update field values, depending on which Master Data version you want to use:

• Creating a VTEX IO service to interact with Master Data v1
• Creating an app to communicate with Master Data v2

These two dynamic settings will be deprecated in Master Data v1.

Existing Calculated Fields and triggers that use the Change field value action will stop working on the same date. Check the What needs to be done? section for more information on how to adapt to these changes.

Calculated Field was a setting within data entity fields that allowed merchants to run C# code to recalculate the field value whenever a new document was added or updated.

This type of field, illustrated below, will no longer be available after June 17. Existing calculated fields will stop working on the same date.

When setting up trigger actions, the Change field value option allowed merchants to add C# code to modify the value of selected fields upon trigger execution.

The Change field value option, illustrated below, will no longer be available when setting up trigger actions after June 17. Triggers created previously with this action will only work until the same date.

If you need to update Master Data field values based on a trigger, we recommend setting up a trigger that sends an HTTP request to a VTEX IO app that communicates with Master Data. This must be done before June 17.

For instructions on how to create this type of app, check the following guides:

• Creating a VTEX IO service to interact with Master Data v1
• Creating an app to communicate with Master Data v2