Required Fields

Required fields must have a non-null value.

• OpenAir sets the data for certain required fields automatically such as the internal ID and other system fields when creating or updating objects.

  Similarly, if a required field has a default value and a value is not passed for this property when creating an object, OpenAir implicitly sets the default value for this field.

  For all other required fields, the client application must explicitly assign a non-null value when creating the object.

• When updating an object, a required field cannot be set to null, and some required fields cannot be changed.

Some fields are required as standard. For most objects, the name or nickname is a required field, for example. Other required fields depend on the business logic configured for your company's OpenAir account.

Note:

Access to certain object types and object properties depend on the business logic configured for your OpenAir account. It may vary depending on the role and access privileges associated with the authenticated user.

Required and read-only properties also depend on the business logic configured for each specific OpenAir account. Some properties such as id, created, and updated are system-generated and always read-only.