First stop in my nullEDGE extended advent calendar: the 2025 Opening Remarks, a warm community‑driven intro that sets the tone with real‑world ServiceNow stories, focus on fundamentals, clean data and a strong ‘always be learning’ vibe.

Using the nullEDGE community conference as an extended advent calendar, I’ll watch one session a day from December to Three Kings’ Day and share short, learning‑in‑public notes to surface high‑signal content that deserves more visibility.

When importing users from external systems, you might have some User IDs that are longer than the 40-character limit in ServiceNow. It can be tempting to increase the size of the “User ID” [user_name] field to fit those longer values. Trust me, don’t do it! Not just because ServiceNow explicitly tell you not to do

Automate ServiceNow code search configuration by updating searchable tables and fields daily with a scheduled job. This reduces manual updates and prevents permission errors using configurable filters. The update set includes everything needed to keep your code search accurate and current.

ServiceNow’s M2M table creation generates field names that work perfectly in your dev instance but silently fail during GitHub deployment to other instances. The sys_ prefix breaks global scope naming rules, causing scripts to fail without errors.

Celebrating my 40th birthday by sharing 40 curated ServiceNow RSS feeds that have taught me something valuable over the years.

Do not use “gr” as a variable name in ServiceNow! Are you convinced yet? If not, let me show you a crazy example.

Learn how to securely connect ServiceNow to GitHub using SSH deploy keys with ECDSA encryption. This guide covers generating SSH keys, configuring GitHub deploy keys, and linking ServiceNow Studio to your repository without using personal credentials.

An 11-year ServiceNow journey summarised in 11 lessons. From Eureka to Yokohama. From junior developer to Certified Technical Architect. From consulting to co-founding my own company.