It is not uncommon to find that there are fields in your CRM that are not being used anymore. While your company might not be using the field anymore, it might still be used in the MadKudu platform based on the configurations created during your onboarding. Thus, before deleting that field from your CRM, read the below to learn how you can safely deprecate a field when MadKudu is integrated to your CRM platform.

Prerequisites

• You are an Admin for your MadKudu account
• You know where to find the pull section in the MadKudu App
• You know where to check your model mappings in the MadKudu App
• You know where to check your model configurations in the Data Studio

1. Check if a field is pulled by MadKudu

In order to check if a field is being pulled by MadKudu, go to the Integrations tab in the MadKudu App.

Select which integration would want to investigate.

Click on 'Pull' to see tables with all of the fields being pulled per object by MadKudu.

👉 If you find that the field you would like to deprecate is being pulled, head to the next step. If it is not being pulled, you can safely deprecate the field 🎉

2. Identify where the field is being used in your model/platform.

If the field you have deleted from SFDC is used in a LIVE model, deleting the field from your CRM can interrupt the scoring process of your model. When a field is pulled by MadKudu the field is not necessarily used in the model/scoring.

To be sure that a field is used in the model for scoring, you would need to check if the field is in any of your mappings.

Your mappings can be checked in the ‘Mapping’ tab in the MadKudu app. You will need to check the Attribute mapping, Audience Mapping, and Conversion mapping. Take note of where you see the field you are interested in deprecating.

3. Update the platform/model

Here are guidelines on what to do based on where in step 2 you saw the field to be deleted:

• If the field was used in Attribute mapping:
  • Check if the mapped Attribute Field Name is used in a LIVE Computation that are not created by default (type Standard) by clicking the LIVE button. This is done in the computations page in the Data Studio. 
    • If no, delete the computation and delete the attribute mapping.
    • If yes, check overrides, signals, and model tree (by clicking on the nodes to see the split conditions) or rules in the LIVE customer fit model. If the computation is used in any of these parts of the model:
      1. update these, either by deleting the configuration or replacing the old field with a new field. If you are going to use a new field, make sure it is mapped in the Attribute mapping. Otherwise, there is nothing to do.
      2. delete the computation that was used in the configuration
      3. delete the attribute mapping configuration of the field
• If the field was used in Conversion mapping → update this conversion mapping definition.
• If the field was used in Audience mapping → update the audience mapping.

4. Ask the MadKudu Support team to stop pulling this field

Please submit a support ticket to our support team and tell them the field you would like to delete and what CRM you are using so that MadKudu can stop pulling it. Once you receive a confirmation from support, then you can safely deprecate the field 🎉