API

System APIs

POST system/dictionary/custom-fields

Creates a new custom field

HTTP method POST
URI https://api.rambase.net/system/dictionary/custom-fields
Supported formats Xml, Html, Json (ex. $format=json)
Successful HTTP status code 201
API resource identifier 2928, version 4

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<CustomField>
2
     <Name
Name

Required/mandatory field

Name of the custom field

Maximum value: 40

Input must match the following regular expression pattern: ^([A-Za-z]+[A-Za-z0-9]*)$

>
{String}</Name>
3
     <Description
Description

Description of the custom field

Maximum value: 4500

This field is optional.

>
{String}</Description>
4
     <Object
Object

Required/mandatory field

Object this custom field is belonging to

Applicable domain values can be found here

>
{Integer}</Object>
5
     <DataType
DataType

Required/mandatory field

Datatype to use for this custom field

Applicable domain values can be found here

>
{Integer}</DataType>
6
     <HasValueList
HasValueList

True if custom field has a valuelist. The domain values will be of object UDF, and field is the name of the custom field.

Default value: False

This field is optional.

>
{Boolean}</HasValueList>
7
     <Publisher
Publisher

This field is optional.

>
8
          <PublisherId
PublisherId

Publisher identifier

Minimum value: 100000

This field is optional.

>
{Integer}</PublisherId>
9
     </Publisher>
10
</CustomField>
1
{
2
     "customField": {
3
          "name
Name

Required/mandatory field

Name of the custom field

Maximum value: 40

Input must match the following regular expression pattern: ^([A-Za-z]+[A-Za-z0-9]*)$

":
"{String}",
4
          "description
Description

Description of the custom field

Maximum value: 4500

This field is optional.

":
"{String}",
5
          "object
Object

Required/mandatory field

Object this custom field is belonging to

Applicable domain values can be found here

":
"{Integer}",
6
          "dataType
DataType

Required/mandatory field

Datatype to use for this custom field

Applicable domain values can be found here

":
"{Integer}",
7
          "hasValueList
HasValueList

True if custom field has a valuelist. The domain values will be of object UDF, and field is the name of the custom field.

Default value: False

This field is optional.

":
"{Boolean}",
8
          "publisher
Publisher

This field is optional.

":
{
9
               "publisherId
PublisherId

Publisher identifier

Minimum value: 100000

This field is optional.

":
"{Integer}"
10
          }
11
     }
12
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$showDomainDescriptions Boolean, optional Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<CustomField>
2
     <CustomFieldId
CustomFieldId

Custom field identifier

>
{Integer}</CustomFieldId>
3
     <Status
Status

Status of the custom field. 4 is active. 9 is deactivated.

Possible domain values can be found here

>
{Integer}</Status>
4
     <Name
Name

Name of the custom field

>
{String}</Name>
5
     <Description
Description

Description of the custom field

>
{String}</Description>
6
     <DataType
DataType

Datatype to use for this custom field

Possible domain values can be found here

>
{Integer}</DataType>
7
     <SortingPriority
SortingPriority

Priority to sort the field

>
{Integer}</SortingPriority>
8
     <HasValueList
HasValueList

True if custom field has a valuelist. The domain values will be of object UDF, and field is the name of the custom field.

>
{Boolean}</HasValueList>
9
     <ValueList>
10
          <Object
Object

Object/archive/context of the values

>
{String}</Object>
11
          <Field
Field

Fieldname of the DOV

>
{String}</Field>
12
     </ValueList>
13
     <Object
Object

Object this custom field is belonging to

Possible domain values can be found here

>
{Integer}</Object>
14
     <ObjectTypes>
15
          <ObjectType>
16
               <Name
Name

Type of object

>
{String}</Name>
17
               <ShowCustomField
ShowCustomField

True if custom field should show. Note that field still exists in database, but it is hidden.

>
{Boolean}</ShowCustomField>
18
          </ObjectType>
19
     </ObjectTypes>
20
     <Companies>
21
          <Company>
22
               <Database
Database

Abbreviation/code to identify the company

>
{String}</Database>
23
               <ShowCustomField
ShowCustomField

True if custom field should show. Note that field still exists in database, but it is hidden.

>
{Boolean}</ShowCustomField>
24
          </Company>
25
     </Companies>
26
     <Publisher>
27
          <PublisherId
PublisherId

Publisher identifier

>
{Integer}</PublisherId>
28
          <Name
Name

Publisher name

>
{String}</Name>
29
          <Description
Description

Publisher description

>
{String}</Description>
30
          <Prefix
Prefix

Unique prefix used for extension objects created by the publisher, e.g. custom fields.

>
{String}</Prefix>
31
          <PublisherLink
PublisherLink

Publisher reference

>
{String}</PublisherLink>
32
     </Publisher>
33
</CustomField>
1
{
2
     "customField": {
3
          "customFieldId
CustomFieldId

Custom field identifier

":
"{Integer}",
4
          "status
Status

Status of the custom field. 4 is active. 9 is deactivated.

Possible domain values can be found here

":
"{Integer}",
5
          "name
Name

Name of the custom field

":
"{String}",
6
          "description
Description

Description of the custom field

":
"{String}",
7
          "dataType
DataType

Datatype to use for this custom field

Possible domain values can be found here

":
"{Integer}",
8
          "sortingPriority
SortingPriority

Priority to sort the field

":
"{Integer}",
9
          "hasValueList
HasValueList

True if custom field has a valuelist. The domain values will be of object UDF, and field is the name of the custom field.

":
"{Boolean}",
10
          "valueList": {
11
               "object
Object

Object/archive/context of the values

":
"{String}",
12
               "field
Field

Fieldname of the DOV

":
"{String}"
13
          },
14
          "object
Object

Object this custom field is belonging to

Possible domain values can be found here

":
"{Integer}",
15
          "objectTypes": [
16
               {
17
                    "name
Name

Type of object

":
"{String}",
18
                    "showCustomField
ShowCustomField

True if custom field should show. Note that field still exists in database, but it is hidden.

":
"{Boolean}"
19
               }
20
          ],
21
          "companies": [
22
               {
23
                    "database
Database

Abbreviation/code to identify the company

":
"{String}",
24
                    "showCustomField
ShowCustomField

True if custom field should show. Note that field still exists in database, but it is hidden.

":
"{Boolean}"
25
               }
26
          ],
27
          "publisher": {
28
               "publisherId
PublisherId

Publisher identifier

":
"{Integer}",
29
               "name
Name

Publisher name

":
"{String}",
30
               "description
Description

Publisher description

":
"{String}",
31
               "prefix
Prefix

Unique prefix used for extension objects created by the publisher, e.g. custom fields.

":
"{String}",
32
               "publisherLink
PublisherLink

Publisher reference

":
"{String}"
33
          }
34
     }
35
}

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return: