Hi all,
So I've got a solution with Cloud Flows along with a few other table customisations. When I try to export the solution to push over to production I'm getting this error:
I don't know what the problem is and the error message literally tells me nothing..
Hi,
i've created the flows outside the solution in my Dev environnement and imported them into the solution.
That is exactely what i feard i guess i have no other choice than rebuild the flows....
Thank you
Hmm never seen that one before. Did you create the flow from within the solution? If not then I highly suggest you rebuild the flow in the solution.
Please download the log file and share the error in that file.
The generic error message is not telling us much
Hello,
I am facing the same issue and i've tried all the steps above its not working for me. In addition of the of the failing export message i have this error :
I'm running into this same issue. Has anyone been able to find a resolution? Microsoft has not been any help so far.
[/quote]Hey bud,
I got a response from Microsoft but I understand it can be quite confusing. So here's what they told me:
Apparently I imported a custom connector into my dev and prod environment and then we did a copy down from production to dev. This was when the issue of Flows happened. Apparently it's because the copy down from prod to dev even though it looks like it's a success doesn't actually copy down the custom connector and hence the connection references. You'd have to reimport the custom connector as a separate unmanaged solution back into the dev environment along with the flows using it for it to actually work.
Microsoft support confused the heck out of me cause they basically gave me a copy and paste answer about deleting, reimporting solutions from target to source without explaining what their definition of the source and target environments were. As I assumed source was the dev environment and target is production. But what they really meant was source is the environment that has the connector (which would be the production environment) and target is the one from which you have to copy down to (the dev).
Kind regards,
I'm running into this same issue. Has anyone been able to find a resolution? Microsoft has not been any help so far.
I had something similar about a month ago. I never found the cause, but I “blame” Microsoft because the where changing a lot things in the background.
I recreated the flow from scratch
Strange issue.
If you find the solution my Microsoft team then please share.
Thanks
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,867 Super User 2024 Season 2
Martin Dráb 229,173 Most Valuable Professional
nmaenpaa 101,156