There are lots of connectors available on the Power Platform (over a thousand), and that leads to a simple question, which one is the best, which i...
For further actions, you may consider blocking this person and/or reporting abuse
Great article! Love the shout out for the forms API, which opens a world of possibilities, like auto scoring quizzes.
Shame this premium connector is now a requirement for that, since it used to be accessible from the SharePoint connector.
Another useful API which, unlike forms, is documented, is the Viva Engage API. This connector works for most endpoints except uploadSmallFile which I think someone forgot has a different base URL...
Awesome write up. Might be good for many non-dev users to touch on the difference between the base and pre-authorized version and why the other one is a hassle (Have to register / authorize yourself for security reasons, etc.) Scopes bit about using base url that are different isn't very clear - unless you are a professional web developer. Really, solid content.
Great call out, was planning to do none pre-authorized but no idea when should have added it here. Yep I went down the rabbit hole on scopes and took it out because to much, but should have found a better balance
This is good
.. I did a project once where I got flow credentials from ms form, then got the manager from office admin action and put the applicant into the relevant security group
cool explaination !!!
Any solution for when you have more than one HTTP Connector in a solution and install users not messing up the URL references when adding the connection references?
Only thing I normally do is add the the setup in the connect reference description. And make sure the name shows url to make it easy to identify in the flow
I've been using this connector to do bulk updates to dataveese by making API calls to dataveese. In a few scenarios, this has helped me decrease the insert time from 30-40 seconds to 4-5 seconds.
When I deploy the app to test environment, the first time the user logs in, it's prompting the user to key in Base Resource URL and Microsoft Entra ID uri (when it's creating the connection). Is this by design ? I am using connection references in my solution.
Has anyone faced this issue before?
I'm afraid so, as the app will use the users connections so requires them to set url. You can move it to a flow called by the app, the. Set the connection to use flow owner not run only user (though the. It will show as flow owner who edited the records)
I am using the connector in the PowerAutomate. I have also deployed the solution to Test Env using service account (to PowerPlatform, I believe its just another account) to make sure that the owners are set to service account for all the objects. The connection is using service account and the correct string values are populated at the connection level. The issue is that the required string values for the connector are not getting passed from the default settings set at connector level to the connections when they are being set for the connection.
learn.microsoft.com/en-us/connecto...
3/4 page down on the above URL suggests that the both the string values are mandatory.
I guess I'll need to bite the bullet.
Regarding "you have to set the scope of the permissions any manual flows/apps require the user to add the url and scope" if you use run only user with a service account you are not prompted to do so since it will use the service account connection!
That's right, but you will still need to set the scope when creating the service accounts connection
{
"host": {
"connectionReferenceName": "shared_approvals-1",
"operationId": "CreateAnApproval"
},
"parameters": {
"approvalType": "Basic",
"ApprovalCreationInput/title": "Internal Order pending for approval - AP25000003 | Test email from BMI Tool",
"ApprovalCreationInput/assignedTo": "abc@xxx.com;",
"ApprovalCreationInput/details": "Test",
"ApprovalCreationInput/enableNotifications": true,
"ApprovalCreationInput/enableReassignment": true
}
}
The user "abc@xxx.com" is trying to run this flow but the node in power automate is giving the error:Action 'Invoke_an_HTTP_request' failed: This request is not assigned to you.
I'm using this for approvals purpose using the URL:api.flow.microsoft.com/providers/M...
My flow is part of a solution and isn't running for users other than me.