In HTTP terms, Content-Type 'header' is used by the client application when it submits data to the server. That being said, one of the most used Content-Types is 'Multipart/Form-Data'. In a 'Multipart' HTTP request, each field to be sent has it's own Content-Type, file name, and data separated by a boundary from the other field(s). With 'Multipart/Form-Data' the … Continue reading Using Multipart/Form-Data in a Power Automate or Logic Apps HTTP Action
When talking to one of our prospective customers, he inquired if we could provide a custom component using PCF that utilized a PDF Viewer in Canvas Apps which could support Annotation, Signatures, etc. With reference to his requirements, I spoke with my new colleagues at PSPDFKit and they had a PDF Viewer available which seemed … Continue reading PSPDFKit Viewer Component for Power Apps
Out of the box Power Automate does not provide an action on a function to directly Convert XML to HTML. In this article, I will demonstrate how we can Convert XML to HTML and then Archive them as PDF using Custom Code Connector.
In this blog post, we will Invoke a Power Automate from Dynamics 365 Or Model-Driven Apps using Form Scripts.
Due to the ongoing COVID situation, teachers have been using Teams and SharePoint to deliver trainings Online. In the SharePoint Site, the Teacher creates a Folders with the library with unique permissions such that Student A cannot access the Folder\Files of Student B. Student usually send their assignments as attachments to their respective teachers in email attachment. The teachers find it difficult to manage the individual attachments.
In this blog post, we will extract PDF form data as XML, Convert XML string to a JSON object and Parse it using Power Automate.
In this blog post, we will extract PDF form data as XML, Parse the XML data and store it a SharePoint List using Power Automate. We will also explore how we can Parse XML data to extract meaningful information using xpath() function and Parse JSON(next blog) action in Power Automate.
In this tutorial, we will learn how to Invoke a REST API with Power Apps and Power Automate. For this demo, we will be using the Muhimbi REST API with the HTTP action and Parse JSON in Flow all while understanding the basics of REST API.
You have authored a Custom Connector and created a Flow associated with a Power Apps which you have then shared with your team or organization. However, when the end users started using the APP they get an authentication prompt, requiring them to enter their credentials or API key which is not ideal as this means setting up a separate, or shared account, for each user in each connector, very inconvenient. In this post, I will explain how we can work around the problem by Sharing the connection of your Custom connector with specific user or the entire organization.
In this post we will consume the Muhimbi SOAP service in an Azure Microsoft .NET Core App Service (as it can easily handle those SOAP webservices through WCF by creating service references) that can further be invoked using a Custom Connector in Power Automate, PowerApps.