Who should attend PL-400T00 Microsoft Power Platform Developer Course
In this course you will learn to build solutions using Visual Studio and Visual Studio Code that include the following: Microsoft Power Platform services, JavaScript, JSON, TypeScript, C#, HTML, RESTful Web APIs, and Microsoft Azure. As a training attendee you must have previous software developer experience using code techniques with modern programming languages such as C# and JavaScript. You must also have a foundational understanding of Microsoft Power Platform and have hands-on experience with the following:
- Developing a data model in Microsoft Dataverse
- Creating tables, columns, and relationships in Microsoft Dataverse
- Building Power Apps canvas apps
- Building Power Apps model-driven apps
- Building Power Automate cloud flows
Prerequisites for PL-400T00 Microsoft Power Platform Developer Course
PL-400T00 Microsoft Power Platform Developer Course Outline
- Imperative versus declarative development
- The three types of variables in Power Apps
- Global variables
- Contextual variables
- Collections
- Additional variable concepts
- Sometimes you need something more than forms
- Use the Patch function to create and edit records
- Delete records from data sources and collections
- Use the Patch function to update a Gallery
- Filter Dataverse choice columns with Power Fx formulas
- Modify choice and choices values
- Work with one-to-many relationships
- Work with many-to-many relationships
- What is relational data?
- Work with relationships in Power Apps
- Microsoft Dataverse for apps makes relationships even easier
- Delegation overview
- Functions, predicates, and data sources combine to determine delegation
- Delegation warnings, limits, and non-delegable functions
- The importance of thinking about performance
- Improve performance with data sources
- Testing and troubleshooting your app
- Use Monitor to troubleshoot app start performance issues
- Optimize App.OnStart
- Data load strategies
- Identify and resolve common problems
- Collaborate by using Monitor
- Set up an app for Application Insights
- View Application Insights data
- Custom logging with trace
- Introducing Power Automate
- Create your first flow
- Troubleshoot flows
- Get started with expressions
- Notes make things easier
- Types of functions
- Write complex expressions
- Dataverse triggers
- Query data
- Create, update, delete, and relate actions
- Overview of Dataverse and the Common Data Model
- Extending Power Platform with Azure
- Power Platform environments
- Solutions overview
- Deploy apps with Package Deployer
- User experience extensibility
- Dataverse extensibility
- Determine when to configure or when to code
- Upload scripts
- Event handlers
- Context objects
- Client scripting common tasks
- Client scripting best practices
- Debugging client script
- Create or edit modern commands
- Work with classic commands
- Use Power Fx
- Power Apps component framework architecture
- Power Apps component tooling
- Component manifest
- Demo of the Power Apps code component
- Create a code component solution package
- Test and debug code components
- Microsoft Dataverse extensibility model
- Event framework
- Plug-ins usage scenarios
- Plug-in execution context
- Insomnia
- Authenticate against Microsoft Dataverse using OAuth
- Use OData to query data
- Use FetchXML to query data
- Call Power Automate actions from the Web API
- Use the Web API to impersonate another user
- Track entity data changes with change tracking and the Web API
- Microsoft Dataverse Azure Solutions overview
- Expose Microsoft Dataverse data to Azure Service Bus
- Write a Service Bus Event Listener that consumes Microsoft Dataverse messages
- Publish Microsoft Dataverse events with webhooks
- Write an Azure Function that processes Microsoft Dataverse events
- Discover Azure Functions
- Compare Azure Functions hosting options
- Scale Azure Functions
- Explore Azure Functions development
- Create triggers and bindings
- Connect functions to Azure services
- Demo of the maker portal experience
- Explore custom connector configuration options
- Use a custom connector
- What are custom connectors
- What is OpenAPI and why you should use it
- Test the custom connector
- Authentication options
- Use APIs with Azure AD
- Configure Microsoft Entra ID authentication
- Share and move between environments
- Use expressions to access runtime values
- Use policies for data conversion
- Configure host URL and routing
- Add or update values
- Use OpenAPI extensions
- Use the dynamic list of values extension
- Use dynamic schema
- Add and remove apps, flows, and entities in a solution
- Edit a solution-aware app, flow, and table
- Build and deploy a complex solution with flows, apps, and entities
- Automate solution management
- Solution layering
- Solution architecture tools and techniques
- Use version control for solutions
Resources
FAQs on PL-400T00 Microsoft Power Platform Developer
This course is designed for software developers with prior coding experience in languages like C# and JavaScript who also have foundational knowledge of Microsoft Power Platform, including hands-on experience with Dataverse, canvas apps, model-driven apps, and Power Automate cloud flows.
Candidates need introductory knowledge of Power Platform and development experience with JavaScript, JSON, TypeScript, C#, HTML, .NET, Microsoft Azure, Microsoft 365, RESTful Web Services, ASP.NET, and Power BI.
The course covers building solutions using Visual Studio and Visual Studio Code, incorporating Microsoft Power Platform services, JavaScript, JSON, TypeScript, C#, HTML, RESTful Web APIs, and Microsoft Azure.
You will learn imperative development techniques for canvas apps, custom data updates using the Patch function, working with Dataverse choice columns and formulas, managing table relationships, and handling relational data within Power Apps.
While the initial modules emphasize canvas apps and Dataverse relationships, the course as a whole is designed for developers extending Power Platform capabilities, including data modeling, custom logic, and integration with external services via code.


