Issue with the Microsoft PowerPoint Add-In // PPT changes file size when cards are refreshed

bogdaniol · 2024-02-05T09:23:35+00:00

There was an error rendering this rich post.

Hi everyone,

Our team is facing a weird issue and we do not know why.

We have three members in the team and one of us has the issue.

Most of the times, when our member with the issue refreshes all cards in the PowerPoint, the size of the PowerPoint increases from 11 MB to 23 MB. Due to this, the exported PDF is 23 MB big.

This is too large to send as an attachment.

Sometimes the size decreased when the cards are refreshed again. The third or fourth refresh usually fixes the issue and the PowerPoint is at 11 MB / the exported PDF at 7,1 MB.

Other times multiple refreshed do not fix the issue.

However, when the other two members refresh all cards, the PowerPoint size never increases. When they refresh the 23 MB PowerPoint the size is reduced to 11 MB again.

The PowerPoint is located on a SharePoint and we all have the same version of PowerPoint. Furthermore, we all have the same OS.

Did anyone experience a similar issue?

What causes the issue and how can we solve this?

Find more posts tagged with

Reports

powerpoint

Accepted answers

ArborRose

Could there be a difference in permissions between users? Does this user have access to something others do not, thus adding to the "weight" of the file?

Things you might want to try:

1. Make sure there is consistent access to the SharePoint location where the file is located as well as associated resources.
2. Check data source permissions. If the Domo cards in the presentation are connected to other data sources or datasets, ensure all members have access.
3. Have all three members in turn, log into the same computer to perform the refresh. If permissions are the same, this would verify there's no other payload as a factor.
4. Test with sample data with a smaller or simplified dataset.
5. Uninstall and reinstall the add-in.

All comments

ArborRose

Are you all using the same environment? Is the other team member on a different system? Have you checked to make sure the add-in used is up to date? Sometimes issues and bugs can be resolved by updating to the latest version.

bogdaniol

We also thought that this might cause the issue.

However, we are using the same environment and the add-in is up to date.

ArborRose