Skip to main content

Hi Community!

Figma Buzz couldn’t have arrived at a better time, it seriously saved me so much work for our new marketing strategy. I’ve been bulk creating hundreds of personalized letters with QR codes, custom images, and data… it’s awesome!

That said, I think I’ve hit the limit in two ways, both with the interface and the export feature, and it’s stopping me from pushing this further.

I’ve bulk created over 200 items, but in grid view, I can’t scroll down to see the last ones. Weirdly, I can scroll way up into empty space, but not down to where my content is. So I can’t properly review everything or select those lower items to export.

Also, even though I created the items in batches of 75–100 and split them into rows, there’s no way to select and export by row. Combined with the scroll issue, this means I can’t get everything into a single file, super frustrating.

Anyone have a better workaround than splitting into multiple files? I’ve got 1,000 more to make in the next few weeks 😬

Thanks!

 

 

Hi ​@Rik2 

 

Thanks for sharing your feedback!

Regarding exporting by row - you're right, this would be a feature request. As a potential solution in the meantime, you could switch to Editor mode where you can export selected assets. I understand this isn't ideal for your workflow, but I'll definitely pass this suggestion along to our product team.

About the scrolling issue - this could be either a bug or a feature limitation. I'm checking with our internal team to get more clarity on this. I'll update you as soon as I have any information I can share.

Thanks for your patience while we look into these items!

 

Thanks for patience !

Toku

Hey ​@Rik2 

 

I wanted to give you an update on the scrolling issue. After checking with our internal team, they've confirmed that this behavior is unfortunately a feature limitation related to how we handle the edges of our 'infinite' canvas.

Our engineering team is aware of this limitation and has it on their radar. To be transparent, this isn't a simple fix due to the underlying architecture, so we don't currently have a timeline for when it might be addressed. That said, we've added it to our list of future improvements.

I appreciate your patience and understanding on this matter.

 

Thanks,

Toku

Reply


Terms & ConditionsCookie settings