Microsoft Flow as an Alternative to SC

(Dan Edwards) #1

While I get the push behind Jitterbit I really wish Microsoft Flow would have landed on the list. I love the connectors & orchestration you can do with this product using Epicor\REST and could just imagine if Epicor was a standard connector offering. I honestly could have seen Microsoft Team, Flow, and Epicor all bundled together within the Azure platform. It has several, if not more, integrations that @josecgomez.sixs mentions and the SalesForce integration is pretty slick.

Announcing Epicor Integration (with 3rd Party System); Early Adopter Program!
(Mark Wonsil) #2

Yes. Yes. Yes.

(Jose C Gomez) #3

Looks like you can make your own

And from a postman collection :scream:


(John Mitchell) #4

My understanding is that Microsoft Flow is just a UI around Azure Functions.

(Dan Edwards) #5

You absolutely can and it works great. It would just be nice to have a little less configuration for those that may not be technically savvy enough to go through the configuration. You can also have gateways involved that allow you to not directly expose your endpoints. Having been through these configurations there are a few tricks that packaging these as pre-configured connectors would save.

(Dan Edwards) #6

Microsoft Flow is basically an Enterprise Integration workflow engine. You can easily do an Epicor to Salesforce integrations or a million other pre-configured connectors to send data to & from.

(John Mitchell) #7

According to Microsoft:

  • Flow is built on top of Azure Logic Apps
  • They have the same workflow designer
  • Connectors that work in one can also work in the other

(Mark Wonsil) #8

Dan, would you mind sharing your Postman collection for a simple service (ABCCodeSvc for example)? I completely share your view here. This would make an excellent Insights talk. (cough cough).

Mark W.

(Dan Edwards) #9

Test.postman_collection.txt (1.0 KB)
I had to rename .txt instead of .json but here you go. The only difference would be your URL

(Jose C Gomez) #10

Pretty awesome @danbedwards hadn’t heard about Flow. Just tested it / threw a simple test together worked great

(Caleb Grundmeier) #11

We are currently using Flow to sync Customers and Contacts to Salesforce. We use Logic Apps to integrate our other internal systems. We use the HTTP Azure AD connector with the free On-Prem Gateway. That way we don’t have to open up the firewall. There is a little extra cost for the connectors but it’s pennies vs Jitterbit or other similar services.

We also have a Flow that will Reset an Dev/Test Environment when we restore a DB. I posted an exported example on this thread: Using REST in an integration

(Mark Wonsil) #12

And Flow is just one function. There is also PowerApps which would allow you to create mobile applications too. The new(-ish) Microsoft Graph is the direction of Microsoft and it would be great to expose our Epicor data in this scenario.

Mark W.

(Stephen Edginton) #13

We are trying to make Epicor as friendly as possible for all of these types of scenarios. Flow is great as is Power Apps and MS Graph and MS Teams!

(Fatboy40) #14

It was all going so well until you mentioned Teams :rage:

(Mark Wonsil) #15

Go on. I’m very interested in your opinion of Teams since that is Microsoft’s TOTAL focus these days. I think the word “Teams” is a marketing nightmare. Are we talking about SharePoint Team sites? The Teams app that’s replacing Skype? The concept of a Team with a SharePoint Site, Planner, etc,? Very confusing. I’m going to start a new thread though…

Mark W.