Skip to main content

Field Configuration

The Field Configuration page lists every field on every entity. Open it from the Entity Registry.

For each row you can set:

  • Field Caption: the label the portal shows.
  • Field Type: how the portal renders it (Text, Number, Select, Date, and so on).
  • Show in Portal: whether the portal shows the field at all.
  • Show on Vendor Form: whether the field is exposed on the public vendor self-service form.
  • Required: forces the user to fill it in before submit.
  • Approval on Change: when an update request changes this field, force a fresh approval cycle.
  • Is Sensitive: hide the value in lists; only show it inside the request detail.
  • Lookup Source: for lookup fields, which BC source list backs the dropdown.
  • Duplicate Match: how strictly to compare this field when looking for duplicates. Strategies are None, Exact Definitive, Exact High, Normalized Name and Contains. Select fields are always skipped because their values are not unique.
  • Include in Sync: whether this field is included in entity-record pushes, versus configuration only.
  • Sync Filter: a BC filter expression restricting which records of this field's value get pushed, for example only rows where a quantity is greater than zero. Combined across every field on the entity type with AND. Usually easier to set from the record type's own Edit Sync Filters action on the Entity Registry, which writes back to this value per row; edit it directly here only when a field is mapped by more than one row and the filter pane can't split it back automatically.
  • Min / Max Value, Max Length: validation constraints. Seeded from BC's table metadata when you first pick a BC field; you can tighten them but the portal will not let users exceed BC's own limits.

When you choose Sync Field Configuration the connector posts the entire field map to the portal. The portal replaces only the rows that were sourced by BC, leaving any portal-only fields an admin added through the portal UI alone.

Lookup data​

Lookup data drives the dropdowns on portal forms (currency code, payment terms, posting groups). Open Lookup Source Mappings to manage which lookup sources are enabled. Each source has:

  • Source Name: the identifier the portal uses.
  • BC Table ID and the field that holds the code and the description.
  • Enabled: include in pushes.

Use the Sync All Lookups action, or the per-row Sync This Source action when you have only changed one list.

Field changes are not pushed automatically. Always finish a session by choosing Sync Field Configuration, and see Day to Day Operations for the order that keeps things consistent for portal users.