💡 Tip: Get Formatted Values to your Web API response from Dataverse.

by Oct 26, 2023

💡 Tip: Get Formatted Values to your Web API response from Dataverse.

We all know the drill – SDK and Power Automate users, you get the luxury of having formatted values by default. 👑

I’m a regular user of the ‘OPEN RECORD IN WEB API’ action in ‘Level up for Dynamics 365/Power Apps’ extension 🚀. The downside? It doesn’t showcase Formatted values, or any annotations for that matter.

What’s needed is a tweak to your request. Simply add the following header:

Prefer: odata.include-annotations=”*”

Now for the real question – how can one do that in the browser? 🤔

Sure, you could tinker around with the developer tools built into your browser, but why settle for the hard way when there’s an easier solution?

Say hello to the ‘Modify Header Value’ extension! With this gem, you can effortlessly specify a custom header addition for every domain. 💎

Learn more here: https://chrome.google.com/webstore/detail/modify-header-value-http/cbdibdfhahmknbkkojljfncpnhmacdek

Did you find this helpful? Drop a comment and let me know! 🙌

# Dataverse, Power Apps
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more