Hi, I have a scenario where I have a bunch of related lists in sharepoint online. For example a list with our Point of Sales addresses, another one with the opening hours of each Point of Sales, another one with the employees, etc...
Our finance department would like to access this info programmatically for some of their reporting needs. One alternative is to tell them to use the sharepoint api and get the data from each list, but I'm looking to offer them an easier solution and my idea was to create a custom 'Point of Sales' connector that has a few simple operations such as /getallpos to get the all the consolidated data in a single call, or /getpos/{posid} to get the info of a single point of sales. This is all internal to our tenant, but I do need to secure some of the data, so I also want to do some authentication of who is calling my connector, because I don't want to give everybody access to the underlying sharepoint lists.
Is a custom connector the right solution for this scenario, or are there better approaches ? Has somebody built a similar scenario sample that I can use to get started ? I've seen a lot of samples accessing external api's but haven't found one that connects to sharepoint.
Stephane
Stephane
Solved! Go to Solution.
Good morning,
Okay now I got a picture.
Let me come to your first question.
It is making a difference if you are using SPO or SP onPrem, cause you would need to establish a connection to your onprem environment via a gateway to fetch data from your SP onPrem. With SP Online you can directly call the SP REST API without entering any firewall secured environments.
But its good that we are talking about SPO!
I also now understood your usecase.
I would say that Power Automate is the wrong technology for your usecase.
I will explain later why I think its not the best idea, but first I would try to show you my idea how
I would build this if I needed to.
So if you want to create this with Power Automate I would concider to do the following:
I would create a flow that will represent your API, you would start with a request trigger (https://flow.microsoft.com/fr-fr/blog/call-flow-restapi/) so your flow gets an rest endpoint.
The trigger is a post endpoint and you can define your JSON Schema. I would give the endpoint the name of your "function" (eg. getallpos or getpos or something else) so the flow knows what to do.
Now you could call your SharePoint lists to fetch the data based on the info you get from the trigger body.
You would need to to some merging operations to build a json that can be send back to the requester.
So you might need some foreach loops etc. It could look like this:
Now you could save the flow and call the endpoint to get the data you requested.
This is working, buuuuut... we have some problems here.
So first the loops inside the power automate are reeeeeally slow. So when you start to merge data from different SharePoint lists and parse your json manually, it will tak you ages for big datasets (lets say bigger then 250 items) So it might happen that your client will run into a timeout when calling the rest endpoint of your flow. In addition your client would need an power automate licensed account. And I am not talking about the E3 lisences, I talk about the per Flow or per User plan.
So all together, yes it is possible, but its not having a good performance and its expensive.
So what are your alternatives?
1. A custom connector itself cannot help you, cause its is not possible to give a custom connector logic, which would give you data from differrent lists at once.
2. Another posiblity is to do this in Azure with a logic app (https://docs.microsoft.com/de-de/azure/logic-apps/logic-apps-overview). Its technically the same. The difference is that you do not need a power automate licensed account in order to call the flow. The performance is still bad (maybe it could be better cause you could use javascript to process your sharepoint items parsing a json), but you could have this at least less expensive.
3. So the cleanest way to implement your a good solution for you would building your own web api. So I would consider doing it with Azure functions. https://docs.microsoft.com/en-us/learn/modules/build-api-azure-functions/ You could easily build up your logic inside the function and then make the endpoint available for your client. This would be clean, not expensive and the performance is much better.
Let me know if my answer was clear or if you need any further assistance on the other topic, cause we are leaving the power automate scope here.
With regards
Kevin
Hello Stephane I think your approach with a custom connector doesnt make sense here.
So what I understood is that you have some sharepoint lists like "Point of Sales" and so on...
First of all, is your sharepoint on prem or is it sharepoint online?
If you need to get access to the sharepoint list you are completely right, you could give your finance department rights to access the list and call the sharepoint rest api.
When it comes to securing data you should secure it on the list itself and not inside the flow.
But let us start form the beginning, when we clear thes questions we will find a solution for you:
SP online or Onprem?
What kind of reports? Excel? PowerBI?
To the finance guys need to get access to the whole data?
What means programatically? Do they use it in some code? PowerShell or Javascript?
if you do not give everybody permissions on the Lists, you should not have the problem to audit the access.
Is this still a Power Automate topic?
I feel that you trying to access SharePoint data from some other code to make reports.
This is more a SharePoint topic and how to secure the SharePoint for your usecase?
Tell me more, I am curious to help you 🙂
With regards,
Kevin
It's SP Online. But it shouldn't matter does it ? If my data was in SQL, I'd still want an API in front of it with operations that make sense to the consuming client ? I want a simple query that gets data from different sources at once. It just so happens that in my case the data sits in SharePoint.
When I say programmatically, I want a downstream system to be able to request data about a point of sales (preferably via a web api call).
I will give the client (user in our tenant) the rights to access the underlying data, without giving open access to everyone. If I were to word it differently:
http://myappapi/getallpos ---> get the data from different sharepoint lists (or whichever datasource the data resides in) & return as one result
http://myappapi/getpos/5 ---> get the data from pos nr 5 and return it to the client
What they do with the data in their own application doesn't really matter to me. Just display it in a custom app (for example (SAP Fiori), use it in a report or whatever their need is.
I've seen other custom connector examples that get information from github, it's just that in my case the data sits in sharepoint within my own tenant. Makes sense ?
Good morning,
Okay now I got a picture.
Let me come to your first question.
It is making a difference if you are using SPO or SP onPrem, cause you would need to establish a connection to your onprem environment via a gateway to fetch data from your SP onPrem. With SP Online you can directly call the SP REST API without entering any firewall secured environments.
But its good that we are talking about SPO!
I also now understood your usecase.
I would say that Power Automate is the wrong technology for your usecase.
I will explain later why I think its not the best idea, but first I would try to show you my idea how
I would build this if I needed to.
So if you want to create this with Power Automate I would concider to do the following:
I would create a flow that will represent your API, you would start with a request trigger (https://flow.microsoft.com/fr-fr/blog/call-flow-restapi/) so your flow gets an rest endpoint.
The trigger is a post endpoint and you can define your JSON Schema. I would give the endpoint the name of your "function" (eg. getallpos or getpos or something else) so the flow knows what to do.
Now you could call your SharePoint lists to fetch the data based on the info you get from the trigger body.
You would need to to some merging operations to build a json that can be send back to the requester.
So you might need some foreach loops etc. It could look like this:
Now you could save the flow and call the endpoint to get the data you requested.
This is working, buuuuut... we have some problems here.
So first the loops inside the power automate are reeeeeally slow. So when you start to merge data from different SharePoint lists and parse your json manually, it will tak you ages for big datasets (lets say bigger then 250 items) So it might happen that your client will run into a timeout when calling the rest endpoint of your flow. In addition your client would need an power automate licensed account. And I am not talking about the E3 lisences, I talk about the per Flow or per User plan.
So all together, yes it is possible, but its not having a good performance and its expensive.
So what are your alternatives?
1. A custom connector itself cannot help you, cause its is not possible to give a custom connector logic, which would give you data from differrent lists at once.
2. Another posiblity is to do this in Azure with a logic app (https://docs.microsoft.com/de-de/azure/logic-apps/logic-apps-overview). Its technically the same. The difference is that you do not need a power automate licensed account in order to call the flow. The performance is still bad (maybe it could be better cause you could use javascript to process your sharepoint items parsing a json), but you could have this at least less expensive.
3. So the cleanest way to implement your a good solution for you would building your own web api. So I would consider doing it with Azure functions. https://docs.microsoft.com/en-us/learn/modules/build-api-azure-functions/ You could easily build up your logic inside the function and then make the endpoint available for your client. This would be clean, not expensive and the performance is much better.
Let me know if my answer was clear or if you need any further assistance on the other topic, cause we are leaving the power automate scope here.
With regards
Kevin
I implemented the single point of sales get request. Works like a charm, and quite fast as well 🙂
I also have a functional GetAllPOS version, but the Apply for Each is horribly slow. I'm still trying to optimize, but haven't got it to respond below 2 minutes yet.
Stephane
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages