วีดีโอ

Hi Simen, Thank you for your inspiration this is a great idea and I will try to post something today around this. Just to answer your questions above so it can help you as quick as possible though I still hope you watch the video to come as I'll try and share more around best practices I have learnt in my decade of experience working with the ServiceNow platform. 1. how do you handle scenarios where you’ve developed something, pushed it to test, and the tester isn’t happy? Would you create a new update set in dev-like a version 2? A. Yes, that would be the way I would suggest doing it , is to create a new update set with the changes and then name it as a V2. Best practice is to always just note the changes the v2 does in the description of the update set. It should also be then mentioned in your release notes that this update set should either go before or after depending on the change as sometimes it could be pre-req rather than an addition. 2. What’s your approach to managing what gets deleted or kept in such cases? A. So I have seen mixed views on this particular question but my stance would always be , if you are deleting records always capture that in the update set and let the update set mechanism deal with those changes. If you are an advanced developer then sometimes you can look at trimming the update sets to remove the customer update of the record so you don't have to capture the delete is an option , however I feel it would be less riskier just to capture the deletion in your newer update set and let the platform handle the rest. 3. How do you handle working with multiple update sets, especially when dealing with different scopes? And what about batching update sets? A. So You have answered your own question here. I would fully suggest to batch the update sets as this allows you to have multiple scopes under a parent. I'll showcase this in the video but just to add you must have a new update set for each separate scope but then batching allows you to have a parent update set where the children update set can have different scopes. I hope that answers all your queries, if not please do let me know. I will also try to go in as much detail and showcase the above in the video to come. Thanks again. Wind

@@wind0004 Hey thanks for that detailed response! 🙏 Looking forward to that video :) I think it will be very beneficial for all the ServiceNow junior devs out there like myself!

Hi Simen, Video has been posted. I hope it helps any questions please do let me know. th-cam.com/video/_CwTSRerMGA/w-d-xo.html

@@wind0004 Awesome! That was fast! Thanks a bunch :)

No problem!

Hi Heeby, That is very odd, as it seems its picking up a very pre-historic date. Could I ask how you are exporting this to Fabric ?

Hi Simen, Thank you for the kind message, its great to hear. Thats an interesting request - let me have a look if I can figure that out and provide you an update.

Hi Simen, So I just posted a video on how to configure the percentage field with the styling. I hope this helps and if you have any further questions please let me know. th-cam.com/video/OvohoZwDRZc/w-d-xo.html

Hi Jacob, so these data preservers are run on the platform instance level so i feel they would still work the same way for an On-Prem set up , if you have seen any differences please do share them

Hi Tinalarue, Thank you for the kind comment, it is much appreciated. By set up - do you mean how to display the search fields under each column , if so it is available just by selecting the magnifying glass next to the first column header in the list view. If not please provide me more details or a use case so I can best help. Thank you for commenting and watching the video.

@@wind0004 Yes, that was exactly what I was looking for. Thank you very much.