Custom Table Not Appearing in Application Navigator — Troubleshooting
You are a ServiceNow developer at a company that manages IT assets. You are asked to create a new table called 'u_software_license' to track software licenses. The table must have fields for license name, vendor, purchase date, expiration date, cost, and number of seats. Additionally, the table must be accessible from the 'Software' module in the application navigator. You have created the table with the appropriate fields. However, after creating the table, it does not appear in the 'Software' module. You verify that the table is set to extend 'Task' and that the application scope is correct. What is the most likely reason the table does not appear in the module?
Quick Answer
This is correct because creating a table and making it visible in a specific module in the application navigator are two separate steps, and it is easy to assume finishing the first one automatically handles the second. A table's structure, including what it extends and which application scope it belongs to, has no direct effect on where or whether it shows up in the navigator; visibility under a particular module depends entirely on a module record that explicitly points to that table. Without that module record, the table has no navigator entry tying it to the 'Software' module, no matter how correctly the table itself was built. It is worth noting that even 'Display in application navigator' only creates a top-level entry for the table, not a placement within an existing module, so that alone would not satisfy this requirement either. Since the scenario already confirms the table correctly extends Task and sits in the right application scope, those structural pieces can be ruled out, leaving the missing module record as the only remaining explanation. Whenever a scenario describes a properly built table that is simply invisible in the navigator where it is expected to appear, check whether a module record has actually been created and linked to that table, since table configuration and navigator visibility are configured independently of each other.
⚠ Common exam trap
Candidates often confuse the 'Display in application navigator' checkbox with module visibility, thinking it controls placement under a specific module, when in fact a module record is required for that.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A module has not been created to reference the new table.
The table does not appear in the 'Software' module because no module record exists that maps the table to that module. To display a table under a specific module in the application navigator, you must create a module record that references the table. The 'Display in application navigator' checkbox only adds the table as a top-level entry, not under a module. Since the user verified the table extends Task and the application scope is correct, the missing step is creating a module record.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The table name 'u_software_license' is not compatible with the Software module.
Why it's wrong here
Incorrect. The table name is compatible; any table can be associated with a module.
- ✗
The 'Display in application navigator' checkbox is not checked on the table configuration.
Why it's wrong here
Incorrect. The 'Display in application navigator' checkbox controls whether the table appears as a top-level navigator entry, not under a specific module. A module record is needed for that.
- ✓
A module has not been created to reference the new table.
Why this is correct
Correct. A module record referencing the table must be created to display the table under the 'Software' module.
- ✗
The table extends 'Task' instead of 'Software', so it cannot appear in the Software module.
Why it's wrong here
Incorrect. Extending 'Task' does not prevent a table from appearing under the Software module; module configuration is independent of table inheritance.
Go deeper
Related to this question
About these practice questions
This SNOW-CAD question is part of Courseiva's 481-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on SNOW-CAD
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An administrator notices that a custom table called 'u_equipment' does not appear in the 'New Record' context menu of the application navigator. What is the most likely cause?
medium- ✓ A.The table was not added to an application menu in the navigation module
- B.The table is extended from a table that is not in the navigator
- C.The table has a business rule that prevents new record creation
- D.The 'Create new' option is inherited from the parent table
Why A: Custom tables must be added to an application menu in the navigation module to appear in the 'New Record' context menu. Option B is incorrect because tables extended from a parent table can appear independently if configured. Option C is incorrect because business rules do not affect navigator menu visibility; they only influence record creation actions. Option D is incorrect because the 'Create new' option is not inherited from the parent table; it requires explicit configuration.
Variation 2. A developer notices that a custom table 'u_project' is not appearing in the 'Create New' menu even though the application scope is set correctly. The table has been created with the 'Create without application' flag unchecked. What is the most likely cause?
hard- A.The 'Extensible' property is set to false.
- ✓ B.The 'Create new record' property is set to false.
- C.The 'Allow Configuration' property is set to false.
- D.The table's roles are not assigned to the developer.
Why B: The 'Extensible' property controls whether other tables can extend this table, not the menu. Option B is correct because the table property 'Create new record' must be enabled for the table to appear in the 'Create New' menu. Option C is incorrect because the 'Allow Configuration' property affects dictionary attributes, not the new record menu. Option D is incorrect because role-based access uses ACLs, but the menu visibility is controlled by the 'Create new record' property.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SNOW-CAD practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CAD exam.