Custom Table Guide · normalized
Custom Table Guide
October 17, 2025
Read original ServiceNow PDF ↗
Rewritten reference, not contractual advice or an estimator. Verify your incorporated agreement and product/SKU applicability. Original PDFs remain on ServiceNow; no source binaries are hosted here.
Effective wording & applicability
Reference only; incorporated agreement and product/SKU applicability must be verified.
SKUs: Not verified; no automatic SKU mapping.
Definitions
- Term
Custom Table / Fields
- Definition
Customer-created or installed non-ServiceNow table used for any purpose unless specifically exempt; custom fields are customer-created non-ServiceNow fields within a Custom Table.
- Source sections
1 Definitions
2.1 Table Extensions
2.2 Table Type
3 Field Limitations
4 Store Downloads
5 Custom Table Assignments
6 Starter Usage Rights
7 Grandfathered Eligibility
- Term
App Engine Starter
- Definition
Studio, Mobile Studio, Guided App Creator and Delegated Development plus explicitly purchased limited custom table entitlement, not general-purpose app rights.
- Source sections
1 Definitions
2.1 Table Extensions
2.2 Table Type
3 Field Limitations
4 Store Downloads
5 Custom Table Assignments
6 Starter Usage Rights
7 Grandfathered Eligibility
- Term
Direct Task Inherited Table
- Definition
Custom Table extending Task with an extension hierarchy consisting entirely of Custom Tables; not Starter-eligible and cannot be grandfathered.
- Source sections
1 Definitions
2.1 Table Extensions
2.2 Table Type
3 Field Limitations
4 Store Downloads
5 Custom Table Assignments
6 Starter Usage Rights
7 Grandfathered Eligibility
- Term
Grandfathered tables
- Definition
Grandfathered Custom Tables may be used for any permissible purpose on a production instance according to the prevailing contract in effect. They are allocated once on migration from a legacy product including App Engine Starter tables. Allocation eligibility is limited to tables created before the migration contract date and used to extend out-of-box workflows; Direct Task Inherited Tables are ineligible. Eligibility is considered in earliest sys_created_on order up to the grandfather entitlement limit. The account's quantity, cutoff date and mapping remain fixed through ownership or structure changes.
- Source sections
1.6 Grandfathered Custom Tables
7 Grandfathered Eligibility
Meter & ratios
- Unit
Not verified
- Definition
No numeric consumption meter; table-count and field ceilings plus classification/use rules are normalized above.
- Limits
- Extensions per listed base table
1000
- Starter custom fields per table
50
- Exempt custom fields per table
50
- Many to many custom fields
3
Scope
Custom table classification, exemptions, assignment and use rights; not a resource-to-SU meter.
Entitlements
Each exempt base table may be extended up to 1000 times: cmdb_ci, cmn_location, cmn_schedule_condition, dl_matcher, kb_knowledge, ml_cluster_detail, sc_cat_item_delivery_task, sc_service_fulfillment_step, scheduled_data_import, sf_state_flow, sys_auth_profile, sys_dictionary, sys_hub_action_type_base, sys_import_set_row, sys_report_import_table_parent, sysauto, syslog. Beyond 1000 requires App Engine or a product with Starter entitlement.
Exempt types: many-to-many registered in sys_m2m.m2m_table (at most 3 custom fields beyond system fields); dictionary-marked remote tables; ar_ tables created by platform archiving; rotated shards listed in sys_table_rotation_schedule; dynamically created application tables marked document tables.
Starter tables and exempt tables each have a 50 custom-field ceiling, subject to the specific 3-field many-to-many restriction.
Production custom tables require explicit assignment to App Engine or express custom-table entitlement from another purchased product.
Starter table quantity comes from each contracted product description and is restricted to configuration/extension of that product’s included entitled applications; exceeding use rights requires App Engine.
Section coverage
- Status
read-and-rewritten
- Sections
1 Definitions
2.1 Table Extensions
2.2 Table Type
3 Field Limitations
4 Store Downloads
5 Custom Table Assignments
6 Starter Usage Rights
7 Grandfathered Eligibility
- Omitted sections
Not normalized.
- Note
All listed source sections reviewed; partial status identifies unresolved source contradictions, not unread sections.
Provenance
- Source url
https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/custom-table-guide.pdf
- Title
Custom Table Guide
- Effective date
October 17, 2025
- Sections
1 Definitions
2.1 Table Extensions
2.2 Table Type
3 Field Limitations
4 Store Downloads
5 Custom Table Assignments
6 Starter Usage Rights
7 Grandfathered Eligibility
- Evidence
Previously preserved private PDF text extraction; no original PDF bytes or redistribution grant.
- Document title
Custom Table Guide
- Source version
Not verified
- Normalization notes
Grandfathered permissible-use rights (section 1.6; preserved extract lines 42–47) are distinct from allocation eligibility (section 7; lines 156–171). Starter usage restrictions remain separately represented (section 6; lines 144–154).
Exceptions
Free partner Store downloads require entitlement for included Custom Tables; free Integration-type apps are exempt unless expanded with additional Custom Tables.
Paid partner apps transacted through ServiceNow Store with positive contract value embed entitlements for included out-of-box tables; additional customer-created tables are not covered by this exemption.
ServiceNow-built out-of-box Store apps do not require Custom Table entitlement unless expanded with additional tables.
Unknowns & limitations
Contract incorporation, purchased quantities, and deployment eligibility are not established; no usage adapter.
Source & provenance
Retrieved: 2026-11-19T08:08:54.236131+00:00
web_extract PDF text; original bytes not downloaded; no raw PDF checksum
Sections: 1 Definitions, 2.1 Table Extensions, 2.2 Table Type, 3 Field Limitations, 4 Store Downloads, 5 Custom Table Assignments, 6 Starter Usage Rights, 7 Grandfathered Eligibility
Literal PDF effective-date wording when present; null means no explicit effective-date label was extracted. See source_version for dated headers or SKU-introduction wording. Contract applicability is separate.
Original PDF checksum: Unavailable; extracted text is not a PDF checksum.