How To become A Dynamics 365 / Power App Developer

by Aug 16, 2022

Simple advice to become Dynamics 365 / Power App Developer when you are a .NET Developer

  • Learn about Entities first, they are like SQL tables with some restrictions and a lot of metadata
  • Power Apps Maker (https://buff.ly/3xUTlOV) is like an SQL Manager studio / editor for your Entities
  • Start from the outside: Leverage the WebAPI first to talk to entities from your own application code
  • Use the Microsoft.PowerPlatform.Dataverse.Client package instead of making your own request to WebAPI
  • Most column data types are normal but learn how to handle the unique EntityReference (=Lookup aka foreign key) and OptionSetType (=like an enum) in Dataverse.

Becoming an expert in Dynamics 365 / Power App Developer is just getting to know Entities (=tables)!

What’s your best piece of advice?

#
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