If you have worked throughout your career in multiple industries including government and are trying to build a Power App for your governments clients that should run on the mobile or desktop client, you might have encountered some connection issues and errors that will not allow you to connect.
With the Microsoft announcement of Code view in Power Apps Studio, developers can not view and use the source code in YAML format and Power FX format. This allows selection of particular controls and see the YAML code that makes up that control
Until recently, there would be a certain subset of functions were you would need to enter the names of the column within double quotes. Starting with the latest version of Canvas Studio (version 3.24042), there will be a syntax change as to how the column names will be displayed within function arguments.
Until recently, if we wanted to call a bound or unbound action from a Canvas app, we would have to create a Power Automate flow that would be triggered from the Canvas App and would then call a bound or unbound action from Power Automate. Not any more…
through an opt-in preview. These controls are based on Microsoft’s Fluent design system, which most of the Microsoft product experiences follow (such as Microsoft Office and Microsoft Teams).
Cards for Power Apps are a new way to design and deliver mini-apps to Microsoft Outlook and Microsoft Teams using Power FX/low-code.
Late last month, the Microsoft Power Platform Customer Advisory Team (PowerCAT) released the Power Apps Creator Kit, which is a set of prebuilt controls and components to assist both citizen and professional developers in their journey of developing Canvas Apps and Custom Pages. In this post I will review a sample application that I created using some of these components.
Whether you are new to developing Canvas Apps or are experienced, the Power Apps Creator Kit from the PowerCAT team has been a big talk in the community. The toolkit provides a list of pre-built controls and components that can be used to design and develop your Canvas Apps and Custom Pages.
In the last few months, I have been working on a migration project for a customer from a legacy system to Dataverse, and one of the functionalities included an embedded Canvas app containing multiple screens and quite a bit of functionality. The main issue that was encountered is that within some geographical regions it was taking a longer time than expected to load the app.
Late November last year, Microsoft released an experimental feature in Canvas apps to allow co-authoring, so that multiple users can work on the app at the same time. Currently, prior to this feature, if a user is working in Canvas Studio, any other user that will try to login to Canvas Studio will be blocked stating that it is locked by the previous user.
