Source Control for Power Platform not working properly

The described behavior aligns with current limitations and expected behavior of Dataverse Git integration rather than a misconfiguration in Azure DevOps.

Key points from the supported model:

1. Single-branch binding per environment/solution
   Git integration for solutions is designed to work with a single branch at a time. The environment/solution is bound to that branch, and all commit/pull operations are scoped to it. Branching and merging (e.g., MASTER → FEATURE) are expected to be handled in Git (Azure DevOps), and then the environment is re-bound if needed. From the documentation:
   • The feature currently works with a single branch that is specified when binding the environment/solution to the repository.
   • Environments can be disconnected and reconnected to different branches, and Azure DevOps is used for PRs and merges.
   Recommended pattern:
   • Connect DEV to a “developer” branch.
   • Use PRs in Azure DevOps to merge into other branches (e.g., MASTER or FEATURE).
   • Disconnect and reconnect the solution in the target environment to the branch that should be the source of truth when needed.
2. Unexpected error on commit in DEV
   The context does not provide a specific root cause for the generic “An unexpected error occurred” message when committing, but it confirms that:
   • After connecting to Git, changes are tracked in Dataverse and committed via the Source control page.
   • Conflicts must be resolved first; then changes should be pulled, validated, and only then committed.
   Given that the commit appears in Azure DevOps, the error is likely in the UI/operation layer rather than the Git operation itself. The supported mitigation path is:
   • Ensure all conflicts are resolved on the Conflicts tab.
   • Pull any updates from Git first, validate the app, then commit again.
   • If the error persists while commits still succeed, this is a platform issue and should be escalated via Microsoft Support.
3. Appaction-related updates and delete prompts in PLAYGROUND
   When pulling updates:
   • The system checks for objects deleted in Git and prompts whether to remove them from the solution (object remains in environment) or delete them from the environment.
   • This is expected behavior: deletions in Git must be reconciled either at the solution level or environment level before the pull completes.
   In the described case:
   • Choosing to delete from the environment triggers an error involving appaction_appactionrule_classicrules and a Delete method not supporting that entity type. This indicates a platform limitation/bug in handling deletions of those specific objects via Git integration.
   • Choosing to remove from the solution (object remains in environment) allows the pull to complete successfully, but the expected merged changes are not visible. This suggests that the incoming changes are primarily deletions or that the environment’s solution state and the branch’s YAML state are out of sync.
   Supported remediation steps within the documented model:
   1. On the PLAYGROUND environment’s solution Source control page:
      • Resolve all conflicts first, explicitly choosing either “keep existing changes” (environment) or “accept incoming changes” (Git) per object.
      • After conflicts are resolved, pull updates again.
   2. If the appaction deletions continue to fail when deleting from the environment:
      • Prefer the “remove from solution” option so the pull can complete.
      • Then manually adjust the solution content (e.g., re-add or remove the relevant components) and commit back to Git.
   3. If the solution still does not reflect the merged MASTER→FEATURE changes after a successful pull:
      • Disconnect the PLAYGROUND solution from Git.
      • Reconnect it explicitly to the FEATURE branch again, ensuring the branch is initialized and up to date.
      • Use Check for updates and Pull once more.
   4. If the behavior persists (especially the appaction_appactionrule_classicrules delete error), this falls outside the documented normal flow and should be handled by Microsoft Support as a product issue.
4. Working model recommendation for the scenario
   Within the supported pattern:
   • Keep DEV bound to a single branch (e.g., a dev branch). Commit all changes from DEV there.
   • Use Azure DevOps PRs to merge from the dev branch into MASTER and/or FEATURE.
   • For PLAYGROUND, either:
     • Bind directly to the branch that should drive it (e.g., FEATURE), or
     • Disconnect/reconnect when switching which branch should supply updates.
   • Always resolve conflicts on the Source control page, pull, validate, then commit.

If the generic commit error in DEV and the appaction_appactionrule_classicrules delete error continue after following the above, the supported next step is to open a ticket with Microsoft Support, as these indicate platform-level issues not resolvable via configuration alone.

References:

• FAQs about source code integration
• Source control repository operations
• Workflow to write, deploy, debug, and troubleshoot X++ code across multiple environments
• Source control for canvas apps
• Context # FAQs about source code integration
• Context # Source control repository operations