Answered

git Source Control still not working properly

(1) Share

Report

Posted on by TL-06050755-0

Hi all

after reading the news in FAQs about source code integration - Power Platform | Microsoft Learn, I was excited that - after having tried this feature in February and facing many issues - this crucial feature can finally be used.

However, I was disappointed to face the following challenges:

1. When trying to COMMIT, I get the error message: "Shared components in solution scope is not allowed. appaction 'Auftragabbrechen!b8f...' (ID=d9416b41-...-...-...) is present in more than one unmanaged solutions: OnOffBoarding. Please remove the component from one of the solution before committing the changes."

That object (of type webresource -> it's a js file) is definitely not appearing in several solutions but only in 1.

2. Oftentimes, disconnecting a solution or environment from a git connection returns an error (e.g. if the corresponding folder/branch was already deleted in Azure DevOps)

3. Column Security Profiles are not supported in git -> why? This is a crucial component in power platform

Thus, I can still not use this crucial feature

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

CU30041725-0 7 on at

Like (0)

Report
Copy link

Link copied!
@TL-06050755-0

Thanks for sharing your experience—you're not alone in facing these challenges. Here's a breakdown of the issues you're encountering with the Power Platform Git integration (as of May 2025), along with insights from the latest Microsoft documentation and community feedback:

1. Commit Error: “Shared components in solution scope is not allowed”

This error typically occurs when a component (like a web resource) is referenced across multiple unmanaged solutions, even if it appears to be in only one. This can happen due to:

Residual metadata: Sometimes, components are technically still linked to other solutions even after removal.

Hidden dependencies: The component might be indirectly referenced by another solution.

Workaround:

Use the Solution Layering view in Power Platform Admin Center to verify where the component is layered.

Try exporting the solution as unmanaged and inspecting the solution.xml to confirm references.

If needed, remove and re-add the component cleanly to a single solution.

2. Disconnecting Git Fails When Folder/Branch is Deleted

This is a known issue. If the Git folder or branch is deleted outside of Power Platform (e.g., directly in Azure DevOps), the platform can’t gracefully handle the disconnect.

Workaround:

Recreate the missing branch/folder in Azure DevOps temporarily.

Then disconnect the Git integration from Power Platform.

After that, you can safely delete the branch/folder again.

Microsoft is expected to improve error handling for this in future updates .

3. Column Security Profiles Not Supported

You're right—Column Security Profiles are currently not supported in Git integration. This is a limitation of the current schema export model.

Why?

These profiles are environment-specific and often tied to security roles and user assignments, which are not easily portable or version-controlled.

Microsoft has not yet provided a timeline for support, but it’s a frequently requested feature. Suggested Action:

Use ALM pipelines or manual export/import for these components until support is added.

Consider submitting feedback via the Power Platform Ideas portal.

Was this reply helpful? Yes No
Suggested answer

CU09120857-0 2 on at

Like (0)

Report
Copy link

Link copied!

For your point #2 about disconnection errors when the Azure DevOps branch was deleted - I've exactly faced and solved this issue!

The problem occurs because Power Platform's backend gets stuck with orphaned configuration records when the linked branch is deleted. I documented the step-by-step manual fix using the Dataverse Web API.

Here's the complete solution:
https://github.com/wukakagit/PowerPlatform/issues/1#issuecomment-3631086256

The fix involves using a Chrome extension to query and update the stuck sourcecontrolbranchconfigurations records. After applying this, you should be able to disconnect and reconnect normally.

Hope this helps you overcome at least one of the blocking issues!

Was this reply helpful? Yes No