Skip to content

Your Own Fields (Custom Fields)

Enable a key-user custom field for the object's API in SAP and MDM adds it to templates, staging columns, lists and Mass Edit within half an hour, or at once on request.

Draft brief for authors. Replace with the final text; keep the structure.

Page type: Task · Audience: Administrator, SAP key user

Contains

  1. In SAP: Custom Fields app → select the field → Enable Usage for the object's OData API → publish. A field not enabled for the API is invisible to MDM.
  2. In MDM: nothing to configure. MDM reads the API's description every 30 minutes (hourly where the provider's scheduler runs on its free plan) and adds the field as a column of every staging table of the object: Staging Records, the template, the lists, Mass Edit.
  3. "Synchronize now": a user with an Edit role, through an assistant (Synchronize Custom Fields) or the discovery API.
  4. Labels follow SAP's label for the communication user's language. A field removed in SAP or disabled for the API leaves the tables at the next run; staged values in that column are gone with it.
  5. Application Logs records every run that changed something under the object. The "synchronization in progress" message.
  • Caution: a published field's length cannot be decreased later; only one publishing runs at a time in SAP.

Related information: custom-fields-in-objects, app-application-logs.

Source in the product repository: customer guide §9; help-portal notes "Custom fields on the API"; .claude/rules/subscription-and-destinations.md (D125, D126, D146).

Last updated: