Custom Field Namespace

How it works

We're not changing any of your existing custom fields or how you add custom fields, but any new custom fields you create will be wrapped (API) when you see them in the API.

In the UI

When you edit a custom field that was added before R21, you'll see that the API Global Namespace checkbox is selected. This means the custom field isn't included in the custom fields namespace, and behaves as it always has. If you deselect this checkbox and save your changes, your legacy custom field will be added to the custom fields namespace.

Newly-created custom fields don't have the API Global Namespace option. They're in the new custom field namespace by default. If you disable the global namespace option for existing custom fields, they'll be placed in the custom field namespace, the checkbox will disappear, and you won't be able to add them back to the global namespace.

Integrations

Your integrations will continue to support the old format as long as the API Global Namespace option is enabled on the custom field. For the new format, we wrap the API for new custom fields for integration objects. We're showing what this will look like in the examples below.

For the API, Coupa supports your existing custom fields in the new namespace, regardless of configuration. In the case where your custom fields are passed in both the new and old formats, Coupa will utilize the new format and ignore the older format.

API example using XML

For the API, new custom fields are wrapped in a parent <custom-fields> attribute.

<custom-fields>
		<custom-field-1>Name of first custom field</custom-field-1>
		<custom-field-2>Name of second custom field</custom-field-2>
</custom-fields>

API example using JSON

For the API, new custom fields are contained in a parent custom-fields attribute.

{
	"custom-fields": {
		"custom-field-1": "Name of first custom field",
		"custom-field-2": "Name of second custom field"
	}
}