Eliminating custom table

[nmsmtys]

Hello all,

we'd like to get rid of as many customizations as possible on our platform. We have a custom table where we're storing transport numbers coming from an external system. The sole purpose of the table is just to store these numbers and possibly connect them with Change Requests.

The requirement is to get rid of this custom table, and store this data somewhere else. The list of transport numbers should be visible from the Change Request form on a related list. The transport number should be stored in a string field (max 15 characters).

Any ideas on how can we store such data without using a custom table? Maybe repurposing an existing OOTB table, or any other ideas?
Thanks

[Rhodri]

I might be inclined to store this in a lookup table instead (table which extends [dl_matcher]). Obviously I'm not aware of your specific licensing scenario so it could be different, but in the past I have mostly seen lookup tables not included in custom table counts.

[Daniel Borkowi1]

Hi @nmsmtys, perfect Use case for a many-to-many table: 

Many to Many Tables: Many to many tables that are registered in the m2m_table field in the sys_m2m table. These tables are restricted to three (3) custom fields in addition to the standard fields created by the system. See https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/custom-table-gu....

Or if you really want to avoid an additional table, use a List field on Change Request.

Greets
Daniel

Please mark reply as Helpful/Correct, if applicable. Thanks!