- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 02:02 AM
is it right? What steps would you follow to create a custom table?
To create a custom table in ServiceNow, navigate to the Application Menu, select the "Tables" module under "System Definition", or use the "Table and Column" module to view and create new tables.
Once in the "Tables" section, click "New" to start creating a new table. You will be prompted to name the table, for example, "Email Issues." The system will automatically generate a table name, such as "u_email_issues", as all custom tables begin with "u_".
If needed, you can extend the table from an existing one to inherit its records and fields. Afterward, you need to manually add columns from the "Columns" section beyond the default ones like "Sys ID".
For example, you might add columns for "Username," "Email," "Country," configuring each field with the appropriate data type, such as "String" or "Choice."
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 06:41 AM
Hi @Sofvrg,
To answer you question at a high level, these steps are correct.
I would however also add the point to ensure prior to creating a table that analysis has been undertaken to ensure an existing table used for the same purpose/data doesn't already exist (or could be leveraged) - this may seem to be an obvious assumption, but you'd be surprised how many times I've seen tables created unnecessarily.
Additionally consider the purpose of any newly created table and the relationship between other tables (should it be extended or not from an existing table such as task)
Once set up, there will be numerous further steps such as ACL's (security), data structure as well as performance (Think of table indexes).
To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.
Thanks, Robbie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 06:10 AM
Hi @Sofvrg
Yes , it all correct.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 06:34 AM
Hi @Sofvrg ,
This is correct. you can refer the below link to get further information:-
Regards,
Nikhil Bajaj
Regards,
Nikhil Bajaj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 06:41 AM
Hi @Sofvrg,
To answer you question at a high level, these steps are correct.
I would however also add the point to ensure prior to creating a table that analysis has been undertaken to ensure an existing table used for the same purpose/data doesn't already exist (or could be leveraged) - this may seem to be an obvious assumption, but you'd be surprised how many times I've seen tables created unnecessarily.
Additionally consider the purpose of any newly created table and the relationship between other tables (should it be extended or not from an existing table such as task)
Once set up, there will be numerous further steps such as ACL's (security), data structure as well as performance (Think of table indexes).
To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.
Thanks, Robbie