Which one I should create Normal Custom Table vs custom Data lookup table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
Hi All,
we have one custom table House Hold Plan , There are 4 choice fields and options would be like below.
Accounts 10 (Account 1, Account 2.....Account 10)
House Hold Cat 1 = 20 (like House Category 1.1, House Category 1.2..etc ...House Category 1.20)
House Hold Cat 2 = 20 (like House Category 2.1, House Category 2.2..etc..House Category 2.20)
House Hold Cat 3 = 20 (like House Category 3..1, House Category 3.2..etc...House Category 3.20)
Concern :
I have a concern we got excel sheet , that excel sheet has 500+ records combinations . some Account, category values repeated , Like this combination there are 500 + records with different combinations
example :
based on this combination I want to populate dropdown options in above "House Hold Categories" fields on Record.
So Now please help me
in Global scope should I create new normal custom table ( with string type fields Account, House Hold Category 1, House Hold Category 2, House Hold Category 3) to maintain this excel sheet data ? loading data in custom table and creating ScriptInclude and Client script and sort drop-down in target fields ("House Hold Categories" fields ) ?
Or
In Global scope Should I Create new custom Data Lookup table( with string type fields Account, House Hold Category 1, House Hold Category 2, House Hold Category 3) to maintain this excel sheet data ? loading data into custom data lookup table and define Data lookup definitions?
Kindly share your thoughts. How Normal custom table/Datalookup custom table works in this case and which one I have to proceed ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @Supriya25
1) As per my knowledge, Custom Data Lookup tables do not count against your production custom table limit, provided they are explicitly extended from the dl_matcher table.
However, if they are not extended correctly, they will consume your custom table entitlements, which can be tracked in Subscription Management.
Note: For any subscription, license, or entitlement related queries , recommendation is to reach out directly to your ServiceNow Account Executive (AE) for the clarification.
2) In which use case, do you need it?
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello @Supriya25 , If you plan to make a decision based on this data, I suggest exploring Decision Tables. I have listed a couple of articles below to help you get started. If you have any questions, please feel free to reach out and I will be glad to assist you.
https://www.servicenow.com/docs/r/build-workflows/workflow-studio/decision-designer-overview.html
If Decision Tables do not fit your needs and you are specifically choosing between a standard custom table and a data lookup table, I recommend going with the lookup approach.
Regarding licensing, the dl_matcher table is exempt from license fees, please refer below:
Regards,
Nishant