Loading...

Why you need the question mark operator in Power Automate expressions

Why you need the question mark operator in Power Automate expressions
Learn why the question mark operator in Power Automate prevents runtime errors when accessing properties that might not exist, and how to use it with coalesce and nested data.

Published on:

Learn more
Manuel T. Gomes
Manuel T. Gomes

Welcome to my website, where I go deep into Microsoft’s technology and show you what I’ve learned over time.

Share post:

Related posts

Power Automate – Analyze processes using object-centric process mining

We are announcing the ability to analyze processes using object-centric process mining in Power Automate. This feature will reach general avai...

1 day ago

Use customized Business Events of Microsoft Dynamics Business Central on Power Automate.

Overview Microsoft Dynamics 365 Business Central allows developers to define custom Business Events using the AL programming language. These e...

13 days ago

Power Automate – Share Process license capacity across workflows

We are announcing the ability to share Process license capacity across workflows in Power Automate. This feature will reach general availabili...

14 days ago

How to Use Static Results to Test Power Automate Flows Without Creating Duplicate Records

When you work with Power Automate, you’ll eventually run into situations where testing your flow repeatedly starts causing real problems in yo...

15 days ago

Power Platform – Alerts for Microsoft Power Automate work queues is now available for public preview

We are announcing the ability to configure alerts for Microsoft Power Automate work queues from the Monitor section of the Power Platform admi...

28 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy