Authorization is a must for APIs, there is no question about that! On the other hand, development and testing becomes more difficult. So I’d like to introduce you to the feature “Authorize” in Swagger UI that I recently discovered. I have to say, I’m impressed! As a developer, I often use Swagger UI to test my APIs, but I’ve always struggle when it comes to authentication. In the past, I couldn’t test my API in Swagger UI because authentication was…
I can’t say this often enough, I love to automate manual repetitive tasks. An automated process save time and reduces mistakes. For that reason, I want to share a new example with you. Moreover, I use the Microsoft Power Platform together with AWS cloud in perfect harmony. So here is the story: some days ago, I stumbled upon a terraforming process for new AWS Accounts. The initial idea was, to prepare reusable and preconfigured building blocks. In other words, my…
After creating my Microsoft OpenAI powered Intelligent Assistant canvas app was still one open question for me, “Can I install and uses my Intelligent Assistant also in Dataverse for Teams?” You might also have the question, “Why would you consider bringing your Intelligent Assistant into DataVerse for Teams?” Well, integrating my Intelligent Assistant into DataVerse for Teams offers several advantages. One of them is that canvas apps empower users to create intuitive and tailored interfaces for data management, enhancing collaboration…
Building microservices instead of a monolithic system is state of the art. These also apply to Power Platform, PowerApps, and Power Automated Flows. You don’t have to solve every problem with the same technology! In other words, sometimes it’s better to build a microservice for Power Platform to improve your apps and flows. This is especially true if your PowerApps or Power Automated Flows require additional power in terms of speed or functionality for a certain data processing. Here, one…
In my session at Dataverse Summit 2022 I also introduced Business Central’s feature, the virtual tables in Dataverse. Virtual tables complement the possibilities such as Data Sync and Connectors to connect both worlds. In my opinion, virtual tables are the best way of integration. Unlike data synchronization, you do not copy the data from one system to another. Furthermore, virtual tables in Dataverse are similar to physical tables in usage and this is a clear advantage in contrast to connectors….
Did you ever create an API based on Power Automated Flows as endpoints? You might be wondering, why would you do that? Trust me sometimes there is a reason. Furthermore, with the growing Citizen Developer Community and the amount of Power Platform solutions being created, this will become increasingly important in the future. If you have joined my session Power Automate Flows as API at the Azure Developer Community Day 2022 at Microsoft in Munich, you already know the story….
Custom connectors are amazing to consume external APIs in Canvas Apps or Power Automate Flows. But what are you doing, when the external API response does not fit for you? To be honest, this week I had the same issue with an own API. I set up my custom connector and everything was fine. The connector worked as expected and my operation provided a response. So far so good… But, on the second look, I found out my response won’t…
Wondering how to access data in Business Central from Dataverse? There are a many ways to combine these two worlds. Join my session to learn how quickly you can connect and transfer data using either connectors or virtual tables. Join my session “Let’s connect: Dataverse & Business Central” during the Dataverse Summit 2022!
Power Apps are amazing! Any Citizen Developer can digitalise fantastic processes if they have the APIs they need. In my session, I show Pro-Developers tricks for providing missing APIs in Azure. Azure Logic Apps, for example, help me to setup quickly and with almost with no code such missing APIs. But the complexity increases mostly during development. A single Azure Logic App suddenly grows into 10 or 20. As a consequence, my Power App has 20 custom connectors. This is…
Custom Connectors and APIs are a pleasure for Power Apps. I can access my needed data, the setup is very fast, and finally I can use the methods of my connector from my Power App. This works fine, except when my API call fails. How can I handle such errors in my PowerApps? Is there something like a Try-Catch-Block? To be honest, it took me a while to find a setup that works for me. So let me first explain…