Creator Kit – Library Control Errors

Posted on 03/11/2023by Angelo

At the time of writing this article, when you add Library Component of Creator Kit, you may find some errors. If you don’t know what Creator Kit is, you can read my article here.

Add control to your App

Add one of Library control to your app. If you didn’t have installed Creator Kit in your environment, you can read this article to do it.

Let’s see how to use this control.

Errors

As you can see, now you have 10 errors on your app. All errors are relative to our Panel Control:

Our control should look like this:

How to fix it

To fix, you should follow these step:

Create a local copy of your control
Fix errors
Use copied control

Let’s start to create local copy. Click on Edit and then Create Copy:

Now you have local copy and you can fix errors:

In this case (But the errors will change depending on the control you have), I fixed:

Button:

If(ThisItem.ButtonType = Primary, ColorValue(Panel_2.Theme.palette.themePrimary))

If(ThisItem.ButtonType = 'Microsoft.CoreControls.Button.ButtonType'.Standard, ColorValue(Panel_2.Theme.palette.themeDark))

Font:

'Segoe UI'

Font.'Segoe UI'

Semibold

FontWeight.Semibold

Transparent

Color.Transparent

Now your control should work. You should see like this:

We can use our version of control:

Considerations

I hope these information can help you…Here you can find official documentations on GitHub for this control.

Contact me for questions! Have a nice day!

Power Apps Power Platform

Power Apps – Named Formulas

Posted on 02/16/2023by Angelo

Today , I want to explain a really cool feature, in order to improve performance of your app and make it “code” more tidier.

NB: This is Experimental Feature, as an experimental feature, do not use named formulas in production apps.

We can use App.OnStart to inizializiate variables, load data and do some operations. These actions my be cause slow starting of your application. Sometimes we use , for example hidden button to write “reusable” code.

Now , we can write formulas and reuse it in any part of our application.

Enabled Named Formulas

Firs of all, you must enable experimental feature. Click on “Settings” and enable it:

Use it

Now, you should see new property of your app, called “Formulas”. Here you can add your formula!

Here you can add your formulas. For example:

ParamID = Param("ID");
UserEmail = User().Email;

But, of course, you can add more complex formula.

Advantages

Why we should use named formulas? let’s see some advantages:

The formula’s value is always available. There is no timing dependency, no event likes App.OnStart should be executed.
Formulas can be calculated in parallel.
The formula’s value is always up to date.
The formula’s definition is immutable. As opposed to variables, the definition in App.Formulas is the only “source of truth” and the value can’t be changed somewhere else in the app.
Calculated when needed. Value are calculated when app need it so this can improve app load time.

Considerations

I hope these information can help you! Here link with additional informations.

Contact me for questions! Have a nice day!

Power Platform

Power Platform – Import solution error 0x80040217

Posted on 02/06/2023by Angelo

Today , I want to explain how to fix Error 0x80040217. If you created custom connector and put it inside solution with for example your flow or your App, may you find in this error, when you try import solution on new Environment:

Error where importing solution with custom connector.

Some note to remember:

You have created custom connector
You have created app or flow who using your custom connector
You have put together in same solution
You have exported it from your environment
You are trying to import in new environment, but you got and error

How to fix It

Really, really simple!

Create a new solution ed import your custom connector. Then , remove it from previus solutions. Basically, you must import your custom connector before, then import your flows or app that using it.

Considerations

I hope these information can help you!

Contact me for questions! Have a nice day!

Power Automate Power Platform

Power Automate – Restore deleted flows

Posted on 01/28/2023by Angelo

Today , I want to explain how you can recover deleted Power Automate flows. PS: If you need recover Power Apps, you can read my article here.

Some note to remember:

You can’t recover your flow if it was deleted more than 20 days ago
You can recover your flow if it was not part of solution (but if did, you can try to open a ticket support)
Default state of recovered flow is disabled
You can recover flow also with powershell commands
You need use Admin user of environment
You can write me for comment to improve quality of my contents 🙂

Create flow to recover deleted flow

Let’s build a new “Instant cloud flow” with manually trigger.

Create new flow — Create new instant cloud flow

Create new flow with manually trigger — Create new instant cloud flow

Now we can add some step to recovery our flow, search “Power Automate Management” and looking for step “List Flows as Admin”, then choose correct Environment and set “Include Soft-Deleted Flows” to Yes.

Now have action to list our flows, included deleted flows. Add “Apply to Each” step (I renamed it “ForEachFlow”) in order to iterate our results and then add “condition” action to filter only “deleted” flow by status property:

Now last step, add action called “Restore Deleted Flow as Admin” set correct Environment (same as step “List flows as Admin”):

and finally run it.

Now , your flow should be appear in list of flow and should be in disabled state:

Considerations

I hope these information can help you to recover your deleted Power Automate Flow…Here you can find official documentation from Microsoft.

Contact me for questions! Have a nice day!

Creator Kit Power Apps Power Platform

Creator Kit – Nav Control

Posted on 01/14/2023by Angelo

Today , we’re introducing one of the menu & nav controls group of Creator Kit: “Nav Control“. Let’s see What is it and how it works. If you don’t know what Creator Kit is, you can read my article here.

Add control to your App

Before use it, you should add it to your app. If you didn’t have installed Creator Kit in your environment, you can read this article to do it.

Let’s see how to use this control.

Nav Control

You can use this control to create a navigation menu in your app. Let’s understand how can we use it. When you add it on your app, you should see something this:

We should set some properties:

Items

Create Table with these attributes:

ItemDisplayName – The Display Name of the menu item
ItemKey – The key of item (must be unique)
ItemEnabled – (Default true) Set to false to disabled
ItemVisible – (Default true) Set to false to hide
ItemIconName – The Fluent UI icon to use (here you can find icons)
ItemIconColor – The color to render the icon as (e.g. named, rgb or hex value)
ItemIconOnly – (Default false) set true to hide text label
ItemParentKey – Render the option as child item of another option
ItemExpanded – Set to false or true if the group should remain collapsed or expanded respectively.

Accourding to documentation, try to put this on Items properties:

Table(
  {
      ItemKey: "1",
      ItemDisplayName: "Home",
      ItemIconName: "Home",
      ItemIconColor: "Green"
  },
  {
      ItemKey: "2",
      ItemDisplayName: "Customer",
      ItemIconName: "People",
      ItemIconColor: "Red"
  },
  {
      ItemKey: "3",
      ItemDisplayName: "Documents",
         ItemIconName: "People",
      ItemIconColor: "Grey"
  },
  {
      ItemKey: "4",
      ItemDisplayName: "Others",
         ItemIconName: "DocumentSet",
      ItemIconColor: "Grey"
  },
  {
      ItemKey: "5",
      ItemDisplayName: "Quick Reference Guide",
      ItemParentKey: "4",
      ItemIconName: "Info",
      ItemIconColor: "Grey"
  }
)

You should see this result:

OnSelect

You can use OnSelect to get selected item and do some actions like change page. As usual, Just to understand , I show selected item display name in a label:

NavMenu.Selected.ItemDisplayName

Results:

Others useful properties are:

Theme : Property to set Json theme on controls, as you can see also in others controls of creator Kit. I usually set it when my application starts, and set it on all controls of Creator Kit who support it. You can create your theme here.
CollapseByDefault: You can set to True or False. Nav remain collapsed or expanded respectively. Individual Item level expand property is respected.

Considerations

I hope these information can help you…Here you can find official documentations on GitHub for this control.

Contact me for questions! Have a nice day!

Creator Kit Power Apps Power Platform

Creator Kit – November Update

Posted on 12/17/2022by Angelo

Let’s see what news are introduced with november update of creator kit. If you don’t know what Creator Kit is, you can read my article here.

New Features

Have been introduced 2 new (in preview) components, SubwayNav and SpinButton:

SubwayNav Control

SpinButton Control

Let’s see a basic introduction to use these controls.

SubwayNav

You can use this control to show a wizard steps in our application. Let’s understand how can we use it. When you add it on your app, you should see something this:

We should set some properties:

Items

Set a Table , with these attributes:

ItemKey: Key of item
ItemLabel: A Display Name of item
ItemState: Icon of the step, it could be one of: “Current”, “Completed”, “Unsaved”, “ViewedNotCompleted”, “Error” , “WizardComplete”

Accourding to source code, try to put this on Items propertie:

Table(
    {
        ItemKey: "1",
        ItemLabel: "Step 1",
        ItemState: "Current"
    },
    {
        ItemKey: "2",
        ItemLabel: "Step 2",
        ItemState: "Completed"
    },
    {
        ItemKey: "3",
        ItemLabel: "Step 3",
        ItemState: "Unsaved"
    },
    {
        ItemKey: "4",
        ItemLabel: "Step 4",
        ItemState: "ViewedNotCompleted"
    },
    {
        ItemKey: "5",
        ItemLabel: "Step 5",
        ItemState: "Error"
    },
    {
        ItemKey: "6",
        ItemLabel: "Step 6",
        ItemState: "WizardComplete"
    }
)

You should see this result:

If you don’t want specify ItemState , you can set empty string (ItemState: “”) , and you’ll see an empty white dot.

OnSelect

You can use OnSelect to get selected item and change page to show next step of your wizard. Just to understand , in this case I saved selected step on variable (Is just an example, you can use Controlname.Selected insted):

UpdateContext({SeletectStep: Self.Selected})

And on label:

SeletectStep.ItemLabel

Results:

Other useful properties are:

Theme : Property to set Json theme on controls, as you can see also in others controls of creator Kit. I usually set it when my application starts, and set it on all controls of Creator Kit who support it.
Subway Nav State: Property to set state on entire controls. You can choose from: “None”, “Errors”, “WizardComplete”

Example of set Subway Nave state property to “WizardComplete”

SpinButton

A spin button is control to allow to add number in small steps. When you add control you should see this:

Principal properties:

Label: Usefull to show a label of control.
Suffix: To add suffix after value.
Theme: As usual, Json theme.
Min: Minimal value to set.
Max: Maximun value to set.
Step: Value to add or Subtracts.

Le’t see an example, I set these properties:

New Features for Existing Components

About esixting control, have been added:

Tooltip for Icon component.
DelayOutput for SearchBox component.

Considerations

I hope these information can help you…Here you can find official release page on GitHub for this update.

Contact me for questions! Have a nice day!

Creator Kit Power Apps Power Platform

Creator Kit – Introduction

Posted on 12/07/2022by Angelo

Today, we’re going to speak about Creator Kit. With this fantastic tool, we have possibility to create Canvas App, with professional look & feel with “Microsoft 365” Style.

What is “Cretor Kit” ?

According to Microsoft , Creator Kit consist in a series of controls , utility and templates , created to increase developer productivity.

All controls are base on Fluent UI Framework , here official documentations.
Is included Template Starter apps , to help you to explore components.

Set Up (Manually)

Follow these Steps:

Download CreatorKit Core Solution from here.
Go to your Environment Settings and Enable “Enable the Power Apps component framework feature”

Enable Power App component Framework Feature — Enable the Power Apps component framework feature

Import Solutions: Go to your Environment and Import Solution (CreatorKit Core Solution)
Optionally, but I suggest you to do it, download CreatorKitCanvas solution and Import It in your environment. You’ll get Template

Utilization

Create new Canvas App
Click on Insert to add controls, and click on “Get more components”

Constrols List — Get more components at bottom

Now you can choose new component from Creator Kit and add them to your App.

Add new components — Controls of Creator Kit

Now you can see new control on control list under “Code components” group.

Flient Tag List component — Fluent Tag List control inside “Code components” group.

Some intresting components

Creator Kit contains around 24 components. You can start study from here. Most intresting component in my opinion are:

AutoWidthLabel is label who expand dynamically his with. You can customize his style by set this properties.
CommandBar classic command bar.

Command Bar

Nav control control to buil navigations menu for your app.

Dialog PopUp to show informations or confirm actions (For example Delete)

As I told you, there are more component and more will added every month. I’m going to create a post every month with description on new comonents.

Contact me for questions! Have a nice day!

Power Apps Power Automate Power Platform

Power Platform – Environment

Posted on 11/04/2022by Angelo

Today, we’re going to speak about Environment. Where people starting to create App or Flow, usually, use Default Environment. But in order to have correct governance or our Power Platform solutions, a good idea (but is not only the one) is create more then one Environment. For Example Dev, Quality and Prod.

What is an “Environment” ?

According to Microsoft , and Environment is a a space to store and share data, app , flows. You can image it as a “Container”.

Each environment can have a single Dataverse DB (but you can create environment withoud it)
Default environment is Shared by all users, in my opinion you shouldn’t use it to develop critical app.

Environment types

Basically we can create 4 kinds of environment.

Sandbox: used for non-production environment but for developing and test. It can be reset or copy.
Production: used for permanent work. You need Power Apps license to create and manage it. It will provided with 1 GB database capacity.
Trial: used for short term testing. It will be cleaned automatically after 30 days. I usually use it to try new features. It can be create also as subscription based, and it can be conferted as production environment.
Developer: you can create a developer plan, follow this one.

Create new Environment

Go to Power Platform admin center: Power Platform admin center (microsoft.com) and click on “New”:

Now you can fill option and create your new environment

You can find usefull information here.

Contact me for questions! Have a nice day!