Namespace identifier › Application scope › Anatomy of an application › Learning about developing on the ServiceNow AI Platform › Building applications

Release: Australia · Updated: 2026-07-09 · Official documentation · View source

Namespace identifier examples

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

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.
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`.
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.
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`.