Forum Discussion
Conditional formatting and tooltips lost after committing .pbip to Fabric Git workspace
Hi everyone, I'm running into an issue with the .pbip format and Fabric Git integration where conditional formatting and tooltip configurations disappear after committing to the workspace.
This report is quite old and originally had a custom theme (.json file) that no longer existed. When I first tried to sync to the workspace it was failing because the theme file was missing. I resolved this by saving the theme again from Desktop, referencing it in report.json and registering the .json file under the report's registered resources.
I wonder if this broken theme reference is somehow related to the conditional formatting and tooltip loss ,perhaps re-importing the theme causes certain visual properties to get dropped during serialization. Not sure if this is a known side effect, but wanted to share in case it helps narrow it down.
As an alternative I tried publishing the report directly to Fabric instead of going through Git. The report shows up correctly in that case, but then I'm unable to download it with the data model included, because the dataset has incremental refresh enabled and the large model format is active, which blocks the .pbix download option. So either way I end up with a limitation: Git sync loses the formatting, and direct publish blocks the download. Has anyone found a clean solution for this, or is the .pbip serialization of conditional formatting a known gap?
Hi drgenius ,
Based on the behavior described, this does appear less likely to be isolated to the theme file itself and more indicative of a serialization gap in the .pbip + Git integration workflow, particularly around how visual level properties like conditional formatting and tooltips are persisted.A few additional checks that may help narrow this down further:
Validate persistence at file level:
After applying conditional formatting/tooltips in Desktop, save the project and inspect the report.json before committing.
Confirm whether those properties are present prior to Git sync
Then compare post sync to see if they are being dropped during serialization or overwritten during workspace ingestionTheme isolation test:
As you suggested, try completely removing the theme reference (report.json + registered resources), reapply formatting manually, and commit again, this helps confirm whether the theme rehydration is interfering with visual property persistenceMinimal repro scenario:
Create a simple .pbip project with one visual, basic conditional formatting + tooltip, no theme applied
Commit via Git and validate if the issue reproduces, this helps determine if it’s a systemic limitation vs report specific artifactCheck for visual type differences:
In some cases, newer visuals or updated formatting panes store properties differently.
Try reproducing with both standard visuals and newer visuals to see if behavior is consistent
Workspace overwrite behavior, If the dataset or report already exists in the workspace, validate whether the Git sync is overwriting visual metadata during deployment rather than merging changes.
Thank you.
4 Replies
Hello,
I’m not completely sure, but this does sound like a serialization gap with .pbip + Git rather than just your theme,sometimes re-linking or regenerating the theme resets visual properties under the hood, so one thing you could try is removing the theme reference completely, reapplying formatting manually, then committing again to see if it sticks
another approach could be testing with a very simple report to confirm if it’s reproducible, that helps rule out report-specific corruption,
honestly this feels more like a platform issue than something you’re doing wrong, I’d probably also raise it with Microsoft or check if there’s an open issue already
Best regards,
DanieleHi drgenius ,
Based on the behavior described, this does appear less likely to be isolated to the theme file itself and more indicative of a serialization gap in the .pbip + Git integration workflow, particularly around how visual level properties like conditional formatting and tooltips are persisted.A few additional checks that may help narrow this down further:
Validate persistence at file level:
After applying conditional formatting/tooltips in Desktop, save the project and inspect the report.json before committing.
Confirm whether those properties are present prior to Git sync
Then compare post sync to see if they are being dropped during serialization or overwritten during workspace ingestionTheme isolation test:
As you suggested, try completely removing the theme reference (report.json + registered resources), reapply formatting manually, and commit again, this helps confirm whether the theme rehydration is interfering with visual property persistenceMinimal repro scenario:
Create a simple .pbip project with one visual, basic conditional formatting + tooltip, no theme applied
Commit via Git and validate if the issue reproduces, this helps determine if it’s a systemic limitation vs report specific artifactCheck for visual type differences:
In some cases, newer visuals or updated formatting panes store properties differently.
Try reproducing with both standard visuals and newer visuals to see if behavior is consistent
Workspace overwrite behavior, If the dataset or report already exists in the workspace, validate whether the Git sync is overwriting visual metadata during deployment rather than merging changes.
Thank you.Hi drgenius ,
We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.
Best Regards,
Chaithra E.Hi drgenius ,
Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.
Best regards,
Chaithra E.
