Namespace identifier examples

The following examples illustrate generating namespace identifiers for applications, tables, and fields.

Table 1. Example namespace identifiers
Action Element generated Explanation
1. Generate a namespace identifier for a private scope application called Book Rooms. x_acme_book_rooms This is a combination of the vendor prefix and application ID.
2. Generate a namespace identifier for a global scope application called Marketing Events. None The system does not generate namespace prefixes for global applications.
3. Add the conference rooms table to the Book Rooms application. x_acme_book_rooms_conference_rooms This table is in the Book Rooms scope so begins with the namespace identifier.
4. Add a Marketing Event table to a global application. u_marketing_event Custom tables in the global scope always use the u_ namespace identifier.
5. Select Book Rooms in the application picker and add the Capacity field on the Conference Rooms table. capacity The field is in the same scope as the table so it does not have its own namespace identifier. However, to dot-walk to the field in a script, you would use the full path including the table namespace identifier: x_acme_book_rooms_conference_rooms.capacity.
6. Select Book Rooms in the application picker and add the Theme field to the Marketing Event table. x_acme_book_rooms_theme The field is in a different scope from the table so it is prefixed with the x_acme_book_rooms namespace identifier. To dot-walk to the field in a script, you would use full path including the field namespace identifier: u_marketing_event.x_acme_book_rooms_theme.
Note: This example assumes that the Marketing Event table allows other application scopes to add fields. For more information, see Application Access Settings.
7. Select Marketing Events in the application picker and add the Theme field to the Marketing Event table. u_theme Custom fields in the global scope use the u_ prefix. To dot-walk to the field in a script, you would use u_marketing_event.u_theme.