Answered

Git source control: initial commit fails

(3) Share

Report

Posted on by JukkaNiiranen

I've been trying to get a solution connected to Azure DevOps Git repo for a few days now. It always fails with:

"The combination of parameters is either not valid or not complete. Parameter name: newCommit"

Not very helpful. Also, after I try to remove the Git connection and start over, the error is:

"Failed to disconnect this solution from Git. Please try again."

It's not a massive solution even. 143 solution objects, 28 of them being Dataverse tables. The total number of changes pending for the initial commit is 1317.

I have tried with different repos on the DevOps side, no impact. Is the source control integration really this fragile?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

Jon Unzueta 1,827 Super User 2025 Season 2 on at

Like (0)

Report
@JukkaNiiranen

That sounds incredibly frustrating — especially when the error messages are vague and the solution isn’t even that large. You're not alone in this, though. Others have run into the same "newCommit" parameter issue when trying to bind Power Platform solutions to Azure DevOps Git repos.

Here’s what might help:

Troubleshooting Steps

Check for unsupported solution components: Some users have found that certain Dataverse components or customizations can cause the initial commit to fail. Try temporarily removing or isolating complex components (like plugins or custom connectors) and see if the commit goes through.

Reduce initial commit size: Even though 1317 changes isn’t massive, the Git integration might be choking on the volume. Try splitting the solution into smaller parts or committing fewer changes initially.

Use a fresh repo and branch: You've already tried different repos, but also try creating a brand-new branch in a clean repo. Sometimes stale metadata or permissions can interfere.

Disconnecting issues: Unfortunately, the disconnect error seems to be a known limitation. Once a solution is bound to a repo, it’s notoriously difficult to unbind without raising a support ticket.The warning “This step cannot be undone” during setup is, sadly, quite literal.

🧩 Workarounds Others Have Tried

Rebinding via support: Some users have had success by contacting Microsoft support to forcibly reset the Git binding.

Manual cleanup: If you're comfortable with backend tweaks, you might try manually removing Git-related metadata from the solution files — but this is risky and not officially supported.

Alternative ALM tools: If this integration continues to block progress, consider using Power Platform’s classic solution export/import with manual Git commits until the binding issues are resolved.

🏷️ Tag me if you have any further questions or if the issue persists.

✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.

❤️ Give it a Like if you found the approach useful in any way.

Was this reply helpful? Yes No
Verified answer

ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report
There was a known issue where too large of a commit would fail as the max commit size is 17MB. It was supposed to be fixed (they now chunk it into multiple small commits then do a squash merge behind the scenes).

Can you try the following?

copy all the components to a different solution temporarily (Solution Components Mover from XrmToolBox helps with that)

Then remove all the components from the binded solution except for a couple and see if a small initial commit works.

If it does then add all the other components back and try the large commit again.

If that still fails then might have to chunk up the commits into smaller batches yourself as a workaround.

Was this reply helpful? Yes No
JukkaNiiranen 28 on at

Like (0)

Report

I got back from my vacation and dediced to try this Git commit once again. The system reported that the solution was not connected to Git (no such actions taken by users) so I decided to do a formal "disconnect from Git" step first. Then, connecting everything as before, waiting for the changes list to stop growing, pushde "Commit" and...

SUCCESS! "Commit Successful. The solution size was too large for a single commit. We processed it as multiple smaller commits and squashed into one: 1234567"

So, it appears MS has fixed whatever issue was blocking the commit before. And just like Chris said, the system does indeed split it into multiple smaller chunks. In this case, there were 9 commits created behind the scenes.

Crossing my fingers that this solution will not get disconnected with future updates anymore...🤞🏻

Was this reply helpful? Yes No