Guidelines on creating custom fields?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2022 07:56 AM
Are there any guidelines/recommendations/best practice on creating custom fields?
I heard someone saying that ServiceNow says not to create more than 25 fields on OOTB forms like INC, PRB etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2022 01:37 PM
Hi, there is a licensing limit to the number of custom fields that you can add to OOB tables.
You can use this link as a guide, but you should always confirm\validate your entitlement with your ServiceNow Account Manager if you are unsure.
Managing your custom tables (servicenow.com)
If the field you require is the same\similar to an existing field on your table, then best practice is to rename\re-utilize OOB fields - but you should always consider long term use of the platform when you do this as re-purposing OOB fields may cause issues later in life if your organization decides to deploy new vendor functionality or revert customizations to OOB behavior.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2022 04:40 PM
Hi Suggy,
I think the recommendation was from the question below. The question is about adding fields to an existing table such as INC and PRB and not about creating a new custom table so table licensing doesn't matter.
The issue with more to do with hard limit of 4096 columns per table, performance of loading a form and user usuablity.
Be aware that table such as incident that has task as a parent table are actually in 1 physical table. So the 4096 columns limitation applies to the total of all columns that have been added to the task table and all of the child tables.
TPH - This table model was introduced in the Dublin release and applies only to the table hierarchy of the task table.there will be one physical db table that stores all classes in a given hierarchy. Currently, this is used on task table. This means, there is one physical database table, “task”, and all child classes of task are store on single physical task table.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0723580
