Refresh
Tools
Screen ID
CST. . . .
Get Link
DAC Schema Browser
Trace...
About...
Upload XML File
Choose File:
max 25000KB
Upload
Cancel
About Acumatica
Profiler
Update History
Expand All
Collapse All
Locales
Get File Link
Report Typo
Print
Export
Plain Text
Word
[Edit]
Naming Rules for Endpoints
When you create a custom endpoint on the
Web Service Endpoints
(
SM207060
) form (either from scratch or by extending a system endpoint), for the names of the entities, fields, actions, and action parameters of the endpoint, and the endpoint name and version, you should make sure to adhere to the following rules:
The name of the endpoint can contain only English letters, digits, underscores, and periods, and cannot start with a digit.
The version of the endpoint can contain only English letters, digits, underscores, and periods.
The name of the entity, field, action, or action parameter can contain only English letters, digits, and underscores, and cannot start with a digit.
The name of the field cannot match any of the following reserved names:
Action
CustomFields
Delete
Entity
ID
Note
ReturnBehavior
RowNumber
The name of the field must be unique among the names of the fields of the entity.
The name of the field that should be used to access a nested entity cannot be
Files
or
Translations
.
The name of the parameter must be unique among the names of the parameters of the action.
The name of the entity or action must be unique among the names of the entities and actions of the endpoint.
The system checks whether the names used in the endpoint satisfy these rules each time you enter the name of a new entity, field, action, or action parameter. You can also validate the endpoint manually, as described in
To Validate an Endpoint
.
Back to Top
Related Articles
To Validate an Endpoint
Internal Link :
External Link :
Public Link :
Close
Naming Rules for Endpoints
When you create a custom endpoint on the [HelpRoot_FormReference\SM_20_70_60|Web Service Endpoints] ([~/?ScreenId=SM207060|SM207060]) form (either from scratch or by extending a system endpoint), for the names of the entities, fields, actions, and action parameters of the endpoint, and the endpoint name and version, you should make sure to adhere to the following rules:[anchor|#_fd2bf273-0424-4d4d-9dc7-30a4703a1378] *The name of the endpoint can contain only English letters, digits, underscores, and periods, and cannot start with a digit. *The version of the endpoint can contain only English letters, digits, underscores, and periods. *The name of the entity, field, action, or action parameter can contain only English letters, digits, and underscores, and cannot start with a digit. *The name of the field cannot match any of the following reserved names: **<tt>Action</tt> ** <tt>CustomFields</tt> ** <tt>Delete</tt> ** <tt>Entity</tt> ** <tt>ID</tt> ** <tt>Note</tt> ** <tt>ReturnBehavior</tt> ** <tt>RowNumber</tt> *The name of the field must be unique among the names of the fields of the entity. *The name of the field that should be used to access a nested entity cannot be <tt>Files</tt> or <tt>Translations</tt>. *The name of the parameter must be unique among the names of the parameters of the action. *The name of the entity or action must be unique among the names of the entities and actions of the endpoint. The system checks whether the names used in the endpoint satisfy these rules each time you enter the name of a new entity, field, action, or action parameter. You can also validate the endpoint manually, as described in [HelpRoot_Dev_Integration\IS__how_Validate_Endpoint|To Validate an Endpoint]. ==Related Articles== *[HelpRoot_Dev_Integration\IS__how_Validate_Endpoint|To Validate an Endpoint]
Send Report
External Link:
Public Link:
Close
Translations
Copy to clipboard (Ctrl+C)
OK
Cancel
Note
OK