ServiceNow Custom Tables 101: What You Need To Know

Подписаться 3,4 тыс.

50% 1

Learn from my mistakes! Understanding the details of the ServiceNow environment you’re working in is crucial. In this video, I share a major mistake I made early in my ServiceNow career. I’ll guide you step-by-step through everything you need to know about ServiceNow Custom Tables to ensure your success.
A few other things to mention:
1) Be aware of field inheritance that occurs when you create a custom table that extends another table. So example, when creating a custom table and you elect to extend from the Task table, your new table starts out with those required fields (as shown in the video), plus all Task fields. This is because your new table is considered a "child" to the Task "parent" table. More documentation about this located here: docs.servicenow.com/csh?topic...
2) There are other types of tables that are exempt that I forgot to mention in the video and they are: Many to Many, Remote, Archive, Rotated Table Shards, Document tables. More information can be found in the "Custom Table Guide" link page 3.
Follow me on LinkedIn - / allenandreas
Twitter/X - x.com/allenovation
Other resources:
ServiceNow - www.servicenow.com
Custom Table Guide: www.servicenow.com/content/da...
Global Default Fields: docs.servicenow.com/csh?topic...
ITSM Pro Entitlements Example: www.servicenow.com/content/da...
Grandfathered tables: docs.servicenow.com/csh?topic...

Наука

Опубликовано:

27 июн 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 20

@Allenovation 6 дней назад

A few other things to mention: 1) Be aware of field inheritance that occurs when you create a custom table that extends another table. So example, when creating a custom table and you elect to extend from the Task table, your new table starts out with those required fields (as shown in the video), plus all Task fields. This is because your new table is considered a "child" to the Task "parent" table. More documentation about this located here: docs.servicenow.com/csh?topicname=table-extension-and-classes.html&version=latest 2) There are other types of tables that are exempt that I forgot to mention in the video and they are: Many to Many, Remote, Archive, Rotated Table Shards, Document tables. More information can be found in the "Custom Table Guide" link page 3.

@bobbybob1932 5 дней назад

Once again I learned something new today, thanks to you. I was under the impression that any tables extending other tables were exempt... and only tables created from scratch were counted as a custom table. As I just finished a story that required me to extend a table not listed in the video - or in your comment - I will make sure to check how many custom tables we currently have and how many we're allowed to have. Thanks again!!

@Allenovation 5 дней назад

I can see why you'd think that! Glad to hear that the video helped though, I hope it all turns out well and they have proper allocations. Either way, great timing and it's smart of you to check their subscriptions!

@7kena7 6 дней назад

Thank you for willing to be vulnerable to share a valuable teaching experience from the past. A lot of your videos cover pertinent issues that noobs like me won't learn from Now Learning or other platforms.

@Allenovation 6 дней назад

You're very welcome. It's viewers and supporters like you that keep me going. Thank you so much!

@OneAndOnlyMe День назад

Ah the good old days where we could create all the tables we wanted in the old licence model. We grandfathered all of our old custom tables when they changed the licensing. I had the foresight to create a bunch of generic custom tables before they changed our license, because you can change the columns still afterwards, just can't create new tables outside of an app (unless they are extended from exempt ones). Tip, if you just need to create a custom table for storing matrix data, for example, a junction table for custom routing data, you can just create and M2M first, then add in your extra columns without needing to create any extra custom tables.

@Allenovation День назад

Great foresight by you for sure! Also, great tip for everyone to consider when they need a custom table for an obscure reason, leverage an exempt table (such as a M2M) to get around the custom table implication. 👏

@im_the_one286 6 дней назад

Thank you for these info , if i didnt watch this video i was about to make same mistake next week 😂 Now i have to check with the client about there licensing Thank you 😄

@Allenovation 6 дней назад

Haha! Glad I could help! Great job on your part for being open to continuously learning for you to come across this video. That’s a big win!

@jodha2381 День назад

Informative video, got a question what if a customer has ITSM Pro(50 tables) as well as App Engine License(75) and now if we need a scoped app, would the ITSM table allocation be utilized in custom scope for the app? or ITSM tables must have ITSM/Global Scope only? Kind of confused and appreciate if you could provide a response on same. Thanks

@Allenovation День назад

Hi, great question! In the purchase order segment of the video when I covered the ITSM Pro App Engine 50 piece, the rest of that sentence said that it was meant for those fulfillers to utilize. Basically, it means, the custom tables allocated per product need to be in support of that product and the same user case (fulfiller) would be the ones who would use that. It doesn’t open the door to a custom app for a completely different purpose. There’s actually separate licensing for that. The App Engine License (75), is most likely what your org purchased for the custom app scenarios. Usually App Engine user licensing is either pay by the user or it’s unrestricted (meaning all users can or could access all custom apps, if applicable). With you all having “75”, it most likely means that you’ll have up to 75 users who could access a or all custom apps. I would try and check your purchase order for specific details or as always, check with the SN account rep for full details!

@gt20396 6 дней назад

Not table related but I created custom ACL rules for a manager who asked her employees have access to certain items, turns out she was trying to circumvent granting them licenses and at the time I didn’t know any better. Thankfully our architect caught it and we cleared them, but I had wondered what would have happened had ServiceNow caught on.

@Allenovation 6 дней назад

That's a great lesson as well and definitely one that we still come across today. There's talk that "read" access...is "fine" to open up, but when it becomes an issue is when users are becoming "fulfillers" (working the records/being assigned the records), then that tends to be where people try to circumvent things. ServiceNow has specific audits they run for that that don't just look for the literal "itil" type role (for example), but they look at access, what roles are associated with that, who has it, and why. Discussions will come about and you'll either have to increase your fulfiller licenses or change the approach. What I've found that works for me is any time I have a question or am doubtful about a requirement like that...just speak to the account rep.

@avishalpatil 5 дней назад

Nice article. Having a doubt here. If we create a custom table by extending an out of box table. Do we still call it as a custom table?

@Allenovation 5 дней назад

Hi. If you create a custom table and extend one of the tables shown in the video in the exempt list (or look in the description of the video for a link to the Custom Table Guide - which has that same exempt list on it), then it’s NOT a custom table. It’ll be exempt. If you create a custom table but extend the out of box Task, or Incident, or something like that, then yes, it’s considered custom and counts.

@avishalpatil 5 дней назад

Understood. Thanks. Keep posting such informative videos.

@Allenovation 5 дней назад

Thank you for your support. It means a lot!