New queryBinary parameter in visuals

Hi ajohns3​,

I am seeing this as more of a report-definition / serialization change than a normal report-authoring change.

Microsoft documents that Power BI report definitions and their JSON schema versions evolve over time, and Fabric Git integration exports those report definitions into Git.

See the Power BI project report-definition documentation.

The interesting part in your case is that queryBinary appears without anyone manually editing the visual.

Robert_KP​'s finding is useful here as well: after Base64 decoding and decompressing the value, the contents appear to contain query information similar to the existing prototypeQuery plus additional binding/execution metadata.

However, I could not find queryBinary documented in Microsoft's current public PBIR/report-definition documentation, so I would avoid assuming that it is a property we should manually edit, remove, or derive ourselves.

For Git, I would handle it like this:

1. Pick one affected report first.
2. Sync/export the Fabric changes.
3. Confirm the report still opens and behaves normally.
4. Verify that the queryBinary additions are the only unexpected report changes.
5. Commit those generated changes separately from your normal development changes.
6. Then apply the same approach to the remaining reports if the behavior is consistent.

I would not repeatedly revert the property if Fabric keeps regenerating it, because that can leave your repository permanently showing differences against the service.

I would also avoid manually modifying the Base64 payload. If this is service-generated report metadata, Fabric/Power BI should remain the owner of that serialization.

So my current interpretation would be:

queryBinary appears to be generated report/query metadata
→ it is not currently publicly documented enough to safely customize
→ validate one report
→ keep service-generated changes together in a dedicated commit
→ do not hand-edit or remove the payload unless Microsoft documents that as supported

The other changes Robert_KP mentioned, such as TMDL culture updates and Dataflow Gen2 schedule metadata, make me even more suspicious that this may be part of a broader service-side serialization/schema update rather than individual users changing their items.

If someone from Microsoft can confirm the rollout, that would be ideal, but until then I would preserve the generated metadata rather than stripping it from Git.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.