Which custom field should I use in 'changes' array for onContactUpdate

App Platform
,
1

The onContactUpdate is duplicating custom fields, one with cf_ prefix and one without. See below for example. Should I use one or the other in order to avoid future code deprecation?

          "changes": {
              "description": [
                  null,
                  "This is about the person."
              ],
              "job_title": [
                  "",
                  "My Work Title"
              ],
              "cf_region": [
                  null,
                  "APAC"
              ],
              "cf_sales_owner": [
                  null,
                  "Steve M"
              ],
              "mobile": [
                  "",
                  "2072248942"
              ],
              "phone": [
                  "",
                  "2026342412"
              ],
              "cf_territory": [
                  null,
                  "North America"
              ],
              "region": [
                  null,
                  "APAC"
              ],
              "sales_owner": [
                  null,
                  "Steve M"
              ],
              "territory": [
                  null,
                  "North America"
              ]
          }
        }
3

Ok, so as a rule of thumb whenever dealing with cf fields try to use the fields with cf prefix as they are the raw field without any manipulation from the marketplace platform.

The reason for the doubling of the field is due to a backend payload change which resulted in these artefacts due to keeping support for old-style apps.

As for deprecation given that many such old apps are in high use, we won’t deprecate this soon. But if any keys are removed in the far future it would be the ones without the cf prefix (for custom fields only).

2 Likes
4

Thanks. I’ll use the cf_* fields.

1 Like