SOLVED

Flow Code View

%3CLINGO-SUB%20id%3D%22lingo-sub-89153%22%20slang%3D%22en-US%22%3EFlow%20Code%20View%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89153%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20thing%20that%20is%20VERY%20nice%20about%20LogicApps%20is%20the%20ability%20to%20go%20to%20the%20%22Code%20View%22%20which%20enables%20a%20team%20to%20take%20the%20JSON%20markup%20for%20a%20process%20and%20use%20that%20to%20technically%20%22import%22%20into%20another%2C%20which%20enables%20a%20nice%20deployment%20strategy%20between%20environments%20(think%20DEV%20%2F%20Stage%20%2F%20Prod).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20feature%20would%20also%20be%20nice%2C%20as%20it%20would%20enable%20people%20to%20promote%20a%20Flow%20to%20LogicApps%20as%20many%20people%20may%20start%20a%20Flow%20from%20a%20%22citizen%20developer%22%20and%20then%20want%20to%20make%20it%20more%20reusable%20and%20shared%20across%20a%20managed%20team%20(even%20more%20than%20just%20the%20Team%20Flows).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20haven't%20been%20able%20to%20locate%20this%20type%20of%20functionality%20request%20on%20any%20published%20roadmap%2C%20so%20figured%20I%20post%20the%20question%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-89153%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92151%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20Code%20View%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92151%22%20slang%3D%22en-US%22%3E%3CP%3EAnd%20even%20better...%20even%20better%20support%20for%20Export%20%2F%20Import%20including%20ready%20to%20port%20to%20LogicApps%20is%20being%20added%20as%20Q2%20updates%20listed%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fflow.microsoft.com%2Fen-us%2Fblog%2Fq2-2017-update%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fflow.microsoft.com%2Fen-us%2Fblog%2Fq2-2017-update%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89172%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20Code%20View%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89172%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20found%20this%20suggested%20idea%20out%20in%20the%20PowerUsers%20community%20section%20(which%20seems%20to%20be%20the%20UserVoice%20equivalent%20for%20Flow)%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fpowerusers.microsoft.com%2Ft5%2FFlow-Ideas%2FPlease-allow-Code-view-of-a-Flow-like-Logic-Apps%2Fidi-p%2F36532%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpowerusers.microsoft.com%2Ft5%2FFlow-Ideas%2FPlease-allow-Code-view-of-a-Flow-like-Logic-Apps%2Fidi-p%2F36532%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

One thing that is VERY nice about LogicApps is the ability to go to the "Code View" which enables a team to take the JSON markup for a process and use that to technically "import" into another, which enables a nice deployment strategy between environments (think DEV / Stage / Prod).

 

This feature would also be nice, as it would enable people to promote a Flow to LogicApps as many people may start a Flow from a "citizen developer" and then want to make it more reusable and shared across a managed team (even more than just the Team Flows).

 

I haven't been able to locate this type of functionality request on any published roadmap, so figured I post the question here.

2 Replies
Highlighted

Just found this suggested idea out in the PowerUsers community section (which seems to be the UserVoice equivalent for Flow):

https://powerusers.microsoft.com/t5/Flow-Ideas/Please-allow-Code-view-of-a-Flow-like-Logic-Apps/idi-...

Highlighted
Best Response confirmed by Brian Caauwe (Contributor)
Solution

And even better... even better support for Export / Import including ready to port to LogicApps is being added as Q2 updates listed here: https://flow.microsoft.com/en-us/blog/q2-2017-update/