"Attachment file size is too big.". Could not export solution

(0) Share

Report

Posted on by jadenkim

i have a solution including 4 components.

two connection references, one cloud flow and one desktop flow.

in order to move desktop flows from dev environment to prd environment, i did export the solution.

when i export the solution i got an error "Attachment file size is too big."

there are one trigger and two actions in the cloud flow, 2000 actions in the desktop flow.

do you have any idea?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi there, have you found a solution to this issue yet? Having the same issue right now. The Desktop Flow itself is very big in size. I can't even export it individually.

Was this reply helpful? Yes No
jadenkim 25 on at

Like
a
(0)

Report
Copy link

Link copied!

@Anonymous

Hi, i didnt get any solution from ms. they recommended me using ALM. but it is not a solution for me.
whenever you get it, please share it all. thank you.

Was this reply helpful? Yes No
Vagiannisg 4 on at

Like
a
(0)

Report
Copy link

Link copied!

any update on this issue? i want to export the solution with only a pad flow and i am getting this error.

Was this reply helpful? Yes No
VJR 7,635 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @Vagiannisg , looks like @jadenkim has already contacted MSFT and their recommendation is to use ALM.

Application lifecycle management (ALM) basics with Microsoft Power Platform - Power Platform | Microsoft Docs

Application lifecycle management (ALM) with Microsoft Power Platform - Power Platform | Microsoft Docs

If you are just having a PAD flow probably you can consider the most easiest way of doing a Cntrl C on your existing flow and Cntrl V in a .text file.

Then use the content in the text file to paste back into another enviornment or flow editor. Just make sure to do a double check to test out if all the contents of the text file contains all the back up like subflows, variables etc.

Was this reply helpful? Yes No
a2sandres 2 on at

Like
a
(0)

Report
Copy link

Link copied!

This solution is too mediocre on the part of Microsoft, since all the mapping of the input and output variables are lost and it would not make sense to have separate environments and apart from that one pays for a license so that it does not work

Was this reply helpful? Yes No
momlo 1,527 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

I agree this is a limitation that should be looked after by MS. But in my guts, i feel (and hope) MS will bake Power Platform Pipelines into the core web platform to address that.

Pipelines allows you t move solutions across different environments with a single click of a button.
This is easy to setup and easy to use ALM that does not require setting up Azure DevOps but instead installing Pipelines PowerApp and setting up environments as managed).
So I would check if ALM Pipelines works for these larger solutions.

If that does not work for you, or you prefer to move solutions manually, you can split your flow into smaller flows and then call one flow from another.

I split my automation this way so I could reuse different parts in different automation. Few examples of these "shared flow" / "libraries" as I call them, that are then called from the actual flow dedicated to some automation.

1. Logon process to the corp web app
2. Logon process to te app X
3. Export documents and register from app X

Was this reply helpful? Yes No