How to Share a Flow for Download or Use on this Forum

[wskinnermctc]

Can anyone give me some ideas of how to share a very large flow with people on the internet? So people on this forum can see it or use it?

I made a large flow that gets a ton of detailed information and makes example MS Graph calls based on a folder selection. I'd like to share it on here, but even if I made screenshots of everything, I don't think people will want to put it all together. 

I've seen where you can get away with copy and paste a scope, but this has different scopes and variables. @takolota  has something like that for Batch Update , but his example is for less steps, so it's easier to copy and paste.

Also, it is meant to be a way to see what you can get for information and provide examples, so it needs to be easy for beginners to open and run.

I have it set up to where the user only has to make a folder selection and site address selection and everything else will run for them.

Flow Overview

Just looking for ideas of how to share this with people.

[VictorIvanidze]

Hi @wskinnermctc,

could you please explain what exactly your flow does? 

[David_MA]

Exporting the flow and sharing it, I would be worried about sharing confidential data such as e-mail addresses, URLs and other information. I then wouldn't want to import anything unless I had an isolated sandboxed environment to import it into.

Something a little less risky from a cybersecurity perspective would be to use PowerDocu to automatically generate documentation of your flow or solution. You can view what this is at https://youtu.be/2-mH8vdVlaM and the software is a free solution in GitHub that we installed on an isolated VM. The documentation is still going to show e-mail addresses, list names and URLs, etc. that are used in the solution. But at least you could go through the generated documentation and replace sensitive information with more generic terms to share in the community.

I have generated documentation from it for solutions with over 15 flows in it, and it creates the documentation in less than a minute. It is certainly much easier than manually creating documentation of each workflow that you can then share with end users.

[wskinnermctc]

It is a flow that doesn't perform a business function, but more like a user help reference. 

For example, when I was trying to make a different way of using an HTTP request to make a document set, I was trying things in MS Graph. This required me to have different id's for the SharePoint sites and drives. As well as fields and values.

Then I was trying to make instructions and had to keep running the flow to get values and screenshots so I wanted all the information listed out in array or csv so I can copy and paste.

Steps of the Flow: 

-For a selected Document Library or Folder In a Document Library

1. Get Web Address and Web Id
2. Get Site Collection Address and Id
3. Get any Parent Site Address or Id
4. Get Folder Properties and Ids
5. Get Folder as a List Item Properties and Ids
6. Get any Parent Folder Hierarchy Properties and Ids
7. Get Document Library Properties and Ids
8. Get List of Document Library Properties and Ids
9. Get List Fields/Columns
10. Get Drive of Document Library Properties and Ids
    • Using HTTP 2.1 or 2.0
11. Get Root Drive Item of Document Library Properties and Ids
12. Get Folder as a Drive Item Properties and Ids
    • Using HTTP 2.0 or 2.1
13. Put all of the retrieved information in separate formats
    1. CSV
    2. Text
    3. Array
14. Creates HTTP Request Examples
15. Creates Graph Explorer Examples that can be copied and pasted into Graph Explorer

It is basically a lot of examples for different types of HTTP requests and Graph Explorer queries that only requires the user to select a Folder and run the flow.

[VictorIvanidze]

Did you try to export it as a zip file?

[wskinnermctc]

Where do I put it after it is a Zip file? How do people import it? 

I don't have any shared box or Github account or anything like that.

[VictorIvanidze]

I mean this:

and this:

[wskinnermctc]

Wow that tool is really great! Thanks for sharing. I don't think I will use it for this example, but I will for sure use it for work things I need to document.

I was looking for something that would help people on this forum import it and then they could run it. 

There isn't any sensitive information in the flow because I used variables for all of the inputs.

[wskinnermctc]

Right I've seen that, but I don't know where I would put the zip file for people on this forum to easily import it.

[VictorIvanidze]

Honestly speaking, too many persons have difficulties while importing...

[wskinnermctc]

Now looking into the code/json information, I'm not sure.

I can see things like tenant Id. And for some reason the Get Folder Metadata has like a history of folders I have searched in the flow.

It's pretty clear for the most part, but there is so much in the flow it would be hard for me to investigate everything to make sure there's no ids or something hidden within it.

[David_MA]

I assumed you knew how to export and import flows and solutions, which is why I offered the automatic documentation tool. You should be able to attach the exported ZIP file to a post such as this unless it exceeds the 5MB file size restriction. The attached flow has nothing sensitive in it and just does the following to see if an e-mail address field is null:

[wskinnermctc]

Thanks for that, I opened it up and looked at the data in notepad and didn't see anything. 

However, when I compare it to my flow in notepad, I can see like my user name and some folder info. I can probably find a way to scrub the folder info by doing something to the step in the flow.

However, I think what might be adding potential sensitive information is the Connections within my flow that go to SharePoint.

I honestly don't know what would be sensitive or not, I just assume hackerman would be able to figure out how to use any siteids or user name in some way, so I don't want it in there at all.

[wskinnermctc]

I agree, I was just going to hope for the best. Or maybe it would work for at least 70% of people ya know.