1️⃣ When you joined the Developer Community and how you first discovered it.

I joined the InterSystems Developer Community about four years ago, around the time we were implementing TrakCare at our hospital. I was actively searching for practical answers, real examples, and best practices beyond official documentation. During that search, I came across the Developer Community, where the Learning resources, documentation, and especially the certification section turned out to be extremely helpful. What started as a place to look up solutions gradually became a space I returned to regularly, not just to read, but to understand how others think, design, and solve real-world healthcare problems using InterSystems technologies.

2️⃣ A meaningful moment or story from your personal journey here.

One of the most meaningful moments for me was realizing that I had moved from being just a reader to an active contributor. Participating in programming contests, writing articles, and completing InterSystems certifications marked an important turning point in my journey. It was not just about achievements, but about the recognition from peers and InterSystems experts that my work added value. That experience gave me confidence and motivated me to take on more challenging projects, especially around FHIR, Embedded Python, and Generative AI.

3️⃣ An article, question, or discussion you consider especially valuable — one you believe others should take the time to revisit.

There are many valuable posts in the Community, but I would especially encourage revisiting articles and discussions around Embedded Python in InterSystems IRIS.  These discussions changed the way I approach solution design by demonstrating how IRIS can combine data management, interoperability, and AI-driven logic in a single platform. They pushed me to experiment with using Embedded Python for validation, transformation, and AI-related tasks within real integration scenarios, leading to more flexible and maintainable solutions.

The Community has been a steady part of my professional journey, and it is great to see how much it has grown over the years.

Hi @Andrew Sklyarov 

Thanks a lot for the kind words and for pointing that out!
You're absolutely right — starting the query with WHERE 1=1 is a smart and simple way to handle dynamic conditions without worrying about when to add WHERE or AND. It definitely makes the code cleaner.

As for %Execute, yes, managing the parameters dynamically is still a bit tricky since the number of placeholders needs to match the inputs. Building the parameter list on the fly could work, but it does add a bit of extra logic.