Summary

Completed

This module follows the Contoso equipment-request code app as it connects to Dataverse tables, calls Dataverse business logic, and carries its configuration from Dev through Test to Production. You now connect a code app to Dataverse data, run Dataverse operations from app code, and configure environment-aware settings that move the same app package across environments.

What you learned

• You add each Dataverse table as its own data source, which generates a typed model and service pair, and you match each task to the right CRUD operation—create, get, getAll, update, or delete.
• You confirm whether a Dataverse action, function, or custom API is bound or unbound before you call it. Then you add the operation and call its generated service to run business logic, such as an eligibility check, instead of duplicating that logic in app code.
• You call the generated RetrieveEnvironmentVariableValue function with a variable's schema name, such as eqp_FulfillmentContact, to read its current, environment-specific value at run time. That way, the same code app package gets the correct value in each environment without a manual edit.

Learn more

• Power Apps code apps overview
• Connect your code app to Dataverse
• Add a Dataverse action or function to your code app
• Create and use custom APIs
• Use environment variables in code app data sources
• Environment variables for Power Platform overview