{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":2294,"path":"application-development/r_ExampleNamespaceIdentifiers.md","title":"Namespace identifier examples","bundle":null,"doc_type":null,"release":"australia","body":"\n# Namespace identifier examples\n\nThe following examples illustrate generating namespace identifiers for applications, tables, and fields.\n\n\n
\n\nAction\n\n\n\nElement generated\n\n\n\nExplanation\n\n
\n\n1. Generate a namespace identifier for a private scope application called Book Rooms.\n\n\n\nx\\_acme\\_book\\_rooms\n\n\n\nThis is a combination of the vendor prefix and application ID.\n\n
\n\n2. Generate a namespace identifier for a global scope application called Marketing Events.\n\n\n\nNone\n\n\n\nThe system does not generate namespace prefixes for global applications.\n\n
\n\n3. Add the conference rooms table to the Book Rooms application.\n\n\n\nx\\_acme\\_book\\_rooms\\_conference\\_rooms\n\n\n\nThis table is in the Book Rooms scope so begins with the namespace identifier.\n\n
\n\n4. Add a Marketing Event table to a global application.\n\n\n\nu\\_marketing\\_event\n\n\n\nCustom tables in the global scope always use the `u_` namespace identifier.\n\n
\n\n5. Select Book Rooms in the application picker and add the **Capacity** field on the Conference Rooms table.\n\n\n\ncapacity\n\n\n\nThe 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`.\n\n
\n\n6. Select Book Rooms in the application picker and add the **Theme** field to the Marketing Event table.\n\n\n\nx\\_acme\\_book\\_rooms\\_theme\n\n\n\nThe 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.\n\n
\n\n7. Select Marketing Events in the application picker and add the **Theme** field to the Marketing Event table.\n\n\n\nu\\_theme\n\n\n\nCustom 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`.\n\n
"}}