Power Automate Tutorial - SharePoint HTTP Connector Part 1- GET
Вставка
- Опубліковано 4 вер 2024
- What’s up friends?!
Welcome to a new Power Automate Tutorial! This time we are talking about the SharePoint HTTP Connector. And more Specifically the GET action.
This tutorial is led by the lovely Ashley Rogers! ( / ashrgrs )
Be sure to check out Ashley's blog for everything from PowerShell to Power Platform: SPinBetween.bl...
To follow me on Twitter head to / jonjlevesque
To make videos like mine head to my shop www.amazon.com...
As always please LIKE & SUBSCRIBE!!
Much Love from Me!
- Jon
lol he said 2020 will be a good year.... little did he know :) 🙀
Omg... i was so optimistic.. and so wrong.. 😂
Love the concise and modular approach of explaining power automate and SP.
it’s hard to simplify a complex process 👌
Ash is a real pro at this stuff for sure!
Thanks Jon for this great video. I have a scenario where I want to get all records but only limited columns. How can I retrieve selected columns
would it be possible to use this to work in PowerQueries for the meta data of a document in PowerBI too? have never been able to figure out how to get to the meta data of documents in SharePoint in Power Query :( That would make it so much easier to base notifications and queries based on the meta data of a document in a Document Library
Great tutorial! Any demo for http + swagger connector? Thanks!
Could you share your Schema content for the Parse JSON?
when used in a for each loop, the sharepoint rest API seems to be slower compared to say a create/update item. I'm reading records from a database and the records go into different sharepoint lists with the same columns. I created a parent/child flow and was passing the listname/listid to the child. The child adds/updates the item via sharepoint HTTP request but it's taking 20 mins to loop through like 7 records. I had to resort back to separate flows for each of the list because of the performance. Any clues?
What is the benefit to using the SharePoint http connector compared to the actions to create/update items that flow provides? Is it performance?
Hey there! It’s more about depth! The http connector can do anything... the built in actions are only a subset of what can be done
Where did you get the Shema for the Parse Json connector....
I want to get an field with HTTP Get and then use HTTP Post to copy the value in an other list. I have a choice field and an person picker (mulit value) to copy. Because those fields do not show up in my create item or get items actions. Now I have build a flow to Get all complete list item but I just need 2 or 3 fields (which are not always filled with data). An one an idea of directions to solve this?
ashley simply impressive. Love the first part :)
Wish they'd do the same with mailchimp, having mad trouble trying to get a http request to get info from a mailchimp list, I'm new to this though and slowly getting it
Can you help with HTTP premium, when authenticating an HTTP POST request?
what if 403 Forbidden error?
Is a connector a group of actions? is that a respectful definition?
A connector is a service which contains triggers and actions wrapped up nicely to interact with Power Automate
@@JonJLevesque so a trigger is not a connector, but a connector can contain triggers, correct? so in theory we can start a flow with an initial trigger, then add multiple connectors following that, that have their own triggers.
Hey Ashley nice video, how are you related with Laura rogers?
Any tutorial on excel http,
Like excel data is there in azure now using http would like to call excel content
cool