Question Regarding Sample Report Referencing Old Visual Version.

[Tung]

Hi everyone

While preparing to submit the updated custom visual to AppSource, I noticed that when saving the sample report, Power BI automatically references the older version of the visual from AppSource (v1.2.0.0) instead of the new version I just exported locally (v1.6.1.2). Nên bị trả trả về lỗi "1180.2.3 Sample File"

Do you know how we should handle this case?

Thank you

Tung.

[v-kathullac]

Hi @Tung  ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,

Chaithanya.

[v-kathullac]

Hi @Tung  ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,

Chaithanya.

[v-kathullac]

Hi @Tung  ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,

Chaithanya.

[v-kathullac · Accepted solution]

Hi @Tungm,

Thank you for reaching out to Microsoft Fabric Community Forum.

The issue you're encountering—AppSource validation error "1180.2.3 Sample File"—is because your .pbix sample file references an older version of your custom visual (v1.2.0.0) instead of the new version (v1.6.1.2) that you're submitting.

How to Fix It

Here’s a step-by-step fix to ensure your .pbix file correctly references the updated .pbviz visual:

1) Open your .pbix file in Power BI Desktop.

2) Delete the old visual

3) Go to the Visualizations pane.

4) Locate your custom visual (v1.2.0.0) and remove it from all pages and from the pane if it appears as imported.

5) Import the new .pbviz (v1.6.1.2)

6) Go to Visualizations → ... (Import a visual from a file).

7) Select your newly built .pbviz file (v1.6.1.2). Re-add it to the report as needed (if it was used in visuals).

9) Save the report after ensuring the visual used is from the local import (v1.6.1.2), not from AppSource.

10) Re-export your .pbix sample file and validate again.

Note:

Power BI sometimes auto-resolves visuals from AppSource, especially if the visual ID is already published.

1) To prevent this Import the .pbviz manually every time from your local system.

2) Ensure that the pbiviz.json file contains the correct:

• GUID
• Visual name
• Version (1.6.1.2 in this case)

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

Regards,

Chaithanya.

[DavidAnthony]

Hi Chaithanya.

Preview

Thanks for your help, here is my other account. I was successful and my product went into production. sorry for the late reply.

Regards,

Tungg.