What: Our plan is to share the pain of going headfirst into the world of Power Pages development, where the stakes are high, the Red Bull is flowing, and the code is… well, let’s just say Kansas is going bye bye. We’ll be covering subjects from committing too much code by mistake to the pains from using fetchxml without a thought for security.

Why: Every developer knows that the best lessons are learned at 3 am with a can of Red Bull in one hand and a rapidly implementing web templates using the other. We want to share these painful tales of woe so that you can avoid our mistakes and save your own Power Pages site (and your sanity).

How: Imagine a late-night talk show, but instead of celebrity gossip, we’re dishing out coding disasters. I’ll have a co-speaker to play the role of the cornered-up developer, a few demo-niton-s, and of course, some tips and tricks on how to save your ass.

Takeaways: The attendees will walk away with a newfound appreciation for best practices in Power Pages development, a healthy fear of creative security settings, and a deeper understanding of why you should always, always double-check your code before committing. So grab a Red Bull (or maybe don’t), and let’s dive into the wild world of Power Pages development!

Takeaways summed up:
- Some best practice tips on Power Pages template development
- Setting up table permissions and displaying data using fetchXML
- Some best practice using code commits and Devops Pipeline deployment
- Some tips on tools developing your site.
- Some emotional scarring...