Workspace Git Integration - Unable to sync a renamed Power BI dataset and report to the workspace.

[dendenharmet]

I'm getting an error that says:

Duplicate logicalIDs

This action can't be completed because the following items have duplicate logicalIDs.

How to fix this issue? I deleted the old file in the workspace but I'm still getting the same issue.

[dendenharmet · Accepted solution]

I was able to solve this by deleting the pbip and its files locally then push and merge it to the branch that is connected in the workspace.

[hski-bayer]

Still struggling with the same issue, open pbip file and SAVE AS pbip with new name doesn't create a new logicalID which results in issues when commit this new pbip to Git and sync the PBI workspace. 
Duplicate logicalIDs, This action can't be completed because the following items have duplicate logicalIDs.

[voytaw]

I found a workaround for this problem, maybe someone else will be interested. The report and semantic model in Power BI Project (.pbip) each have their own LocalID. These LocalIDs are somehow related, but it's not clear to me exactly how. Therefore, if you currently (December 2024) want to synchronize multiple Power BI Projects (.pbip) via Git/GitHub that were originally created as one, later copied and when you try to synchronize you get the error "Duplicate logicalIDs, This action can't be completed because the following items have duplicate logicalIDs. ", it is not enough to simply change the LocalIDs in the .platform files that are located in the <your project>.Report, <your project>.SemanticModel directories. Even though it's a valid GUID.

When I try to open a project with such manipulated LocalIDs in Power BI Desktop, I get the error "Cannot oper report, Cannot read '<path to your project>\<your project>.Report\.platform': Required properties are missing from object: logicalID, line 7, position 13."
The trick I use is to open a new blank project in Power Bi Desktop, name it the same as the one with the duplicate localID, and save it in a temporary directory as .pbip. I then copy the two .platform files from it into <your project>.Report, <your project>.SemanticModel directories. Synchronization with GitHub then works and further development can continue in Power BI desktop.

[hski-bayer]

The logicalId is actual a GUID. You can generate a new GUID and modified manually the save as / copy of a PBIP report and semantic model using lot of possibilities e.g. ADO PowerShell task https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/new-guid or use online tool like https://www.guidgenerator.com

[dendenharmet · Accepted solution]

I was able to solve this by deleting the pbip and its files locally then push and merge it to the branch that is connected in the workspace.

[WilkoH · Accepted solution]

FYI, did not work for me...

However, in local file system I tweaked

*.Dataset/item.config.json
*.Report/item.config.json

and bumped up the logical ID by one... So far no issues with this...

[EvanSkam]

For whomever this may help. I was able to find the logicalID inside the .platform file inside the *.Report directory where my .pibp file is saved.

I incremented it by 1 and it allowed me to sync.

Edit:
Apparently whenever you save, the LogicalId value needs to be re-updated in the .platform file as it resets to the old value.
A tad annoying. It'd be great if duplicating reports and putting the duplicates under source code control was less fussy.