Cards in Power Apps

October 28, 2024October 28, 2024 priyeshwagh777 CRM with .NET Web Applications Adaptive Cards, cards in power platform, power apps, Power Automate

Cards in Power Apps can get you to send Adaptive Cards in Teams chats or channels without having to leave Power Platform to make your card!

Yes, till recently I was having a hard time to make an Adaptive Card in the Adaptive Cards Designer which is outside of the context of Dynamics/Dataverse and then embed it into Flow to be sent to a User – until Cards in Power Apps came along!

Let’s see how we can get started with the same and create our first Card and send in a Teams Chat!

Create a Card in Power Apps Maker Portal

Given you have appropriate access to create and view Cards, here’s how you can create your Card in Power Apps Maker portal –

Navigate to Power Apps Maker Portal (https://make.powerapps.com/) and select the right environment with Dataverse in which you want to create your Cards.
When you click on + New Card, Cards will ask you to name it and add a description.
And once you create – you’ll be taken to the Card Studio.
One the left hand side, you can see the menu which you can identify what the Card can be configured to do.
To keep the function of the Card example, simple – I’m only displaying the logged in user name on click of a button.
Notice that on the right hand side, you have different ways to deploy this Card – like in a Teams Chat.
When in Play Mode, you’ll get to use the Card as it would work when deployed (or sent to a User, in this case), notice on the right hand side, you get a way to deploy the Card whether in a Chat as a link or through a Flow.

In this example, I’ll choose a Flow.
Now, it’ll initialize a Flow template with necessary steps.
When ready, it’ll give this template for me to complete the Flow.

Now, in the next section, let’s continue to finish the Flow and send it to an actual user. (Myself 😊)

Sending a Power Apps Card to Teams Chat

Now, let’s work on our Flow to be ready to run –

First step is to Initialize the Card itself with an instance of the Card. Here, we’ll select the Card we just created.
In the second step, you can actually choose who should the Card go out as.
Then, it as ask what should should it post into. I’ve selected Chat with Power Apps since I wanted it to as a personal chat.
Finally, it also needs a recipient – I’ve selected myself here to test it out.
Now, when I run the Flow, I receive a chat message from Power Apps like below –
And it then runs the Card itself! When I click the button as configured, it’ll read the user and display the name.

Here’s the result!

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Recycle Bin in Dynamics 365 CRM | [Preview]

August 11, 2024 priyeshwagh777 D365 Admin Center, Power Platform Admin Center Dataverse, Dynamics 365, power apps, Power Automate, Power Platform, power platform ad, Power Platform Admin Center, recycle bin for dataverse, restore in dynamics crm, restore records

Now, you can retrieve deleted records up to 30 days in Dynamics 365 CRM /. CE apps.
Here’s how you turn this feature on!

Enable Recycle Bin

Here’s how you can enable this given you have the correct Dynamics 365 System Administrator privileges –

Go to the Environment’s Settings in Power Platform Admin Center (https://admin.powerplatform.microsoft.com/)
Now, expand Product section and go to the Features option.
When you scroll to the bottom, you’ll see Recycle Bin option as a feature. At the time of this blog post, the feature is in Preview – Hence, this is not recommended for production purposes yet.
By default, it’s turned Off.
Once you flick the switch, you’ll be asked for number of days the data has to be retained for. I’ll enter 30 here and then scroll to the bottom and save the setting.
Once saved, you can go to your environment and test this on a sample record. See the section next.

Deleted Records

Now, since this is enabled and post that when you delete records, here’s how you can find them for the number of days you’ve configured Recycle Bin for –

For example, this is the Account record you want to delete.
Go to the View Deleted Records section in the in your environment’s Settings area.
You’ll see the Deleted records which you can select and choose to Restore.
Confirm.
Upon Restoring, they’ll appear where they were originally supposed to exist.

Because this feature is still in Preview, here’s Microsoft’s Documentation on the same with listing of some known issues as well – https://learn.microsoft.com/en-gb/power-platform/admin/restore-deleted-table-records?WT.mc_id=DX-MVP-5003911

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Create a Custom Connector For Power Automate & Power Apps

July 15, 2024 priyeshwagh777 Azure Functions, Customizations, Microsoft Azure, Microsoft PowerApps, Power Automate, Power Platform azure, custom connector, Dynamics 365, Microsoft Azure, power apps, Power Automate, Power Platform

One of the most important qualities of extending capabilities of any platform is being able to add Custom code and make it available to wider use cases.

In this case, it’s a custom code that is encompassed in a Custom Connector in Power Platform and made available to Power Automate or Power Platform.

Use Case

The purpose of my custom connector is to call my hosted custom code in Power Automate or Power Apps.

For this example, I’ve created a simple Azure Function that just returns a value – just to test the working of the Custom Connector. Of course, your use case is to be able to connect to the hosted app, expect it to process the business logic which you intend to do and return back the results.
So, in my case – my Azure Function will simply greet the name passed to it.

See the Postman test below –

Now, let’s make a Custom Connector that will execute this Azure Function in your Power Automate.

Create Custom Connector in Power Apps / Power Automate

You can either make the Custom Connector from the Power Automate portal or the Power Apps Maker portal, both are the same things. Let’s see this example from Power Apps portal –

In this use case, I’m in a Solution in Power Apps / Power Automate. Open the one in your case since you can’t create a Custom Connector from outside a Solution any longer.
Now you can drop down from New and see in Automation menu that you can create a Custom Connector
Now, you’ll be required to enter the name of the Connector itself and other details like a PNG icon for it, Description etc.
Now, below is the info that I filled in. I’m calling it Data Transporter and have selected an Icon which should make me easy to recognize my connector in Power Automate and Power Apps and enter enter the details of my hosted Azure Function which is authenticated using an API Key.
So, here’s what my info looks like –
Now, when I click on Security after filling all the info, the type of Authentication I used in this case if API Key, yours could be different depending on what your custom application is configured to work with –
It’ll ask you to fill in the information so that it appears as parameters to fill in for the Custom Connector when the end user will work on their Flows/Apps.
The info I’m choosing to fill is this – I’m giving a name to the parameter to indicate what info is required. The actual parameter name required by the Azure Function, in this case – it’s ‘code’ and since I need to pass the API key in Query string, I’ve selected Query instead of Header.
When you go to the next part, i.e. Definition, make sure you also give a Name to the Custom Connector already. Before your lose the info you’ve already entered. Make sure you also click on Create Connector

Once you click on Create connector, it’ll create it in a few moments.
Now, since you are aware of Triggers and Actions from using Power Automate – in this use case, my Custom Connector is designed to be an Action i.e. when called/used in Power Automate, it’ll simply perform the operation it’s designed to do.
Hence, I’m selecting an Action here.
When I select New Action from the left hand pane, it’ll open up information for me to fill out to describe the Action.
Now, since this will appear as a listed item in Actions in my Power Automate connector, I’m filling in this info (and we can check later how it appears).

Next, I’ll click on + Import from sample as it’ll give me a place to enter a sample for the request to call my hosted Azure Function.
Next, I’ll pass these values as I did in Postman to create the sample. Once done, I can click on Import.
When I import, I’ll the request parameters set in the Custom Connector based on the sample I entered.
Next, I’ll scroll down to ensure that all validations are perfect and I needn’t fix anything.
Next, I’ll skip AI Plugins step and also the Code step since I want to keep this example concise and to the scope of the hosted Azure Function only.

And this is skipped too –
Now, the final step is to Test the Custom Connector. The Editor will ask you to Update connector before you can Test. Then, in order to begin testing – you’ll need to first create a Connection using New Connection button as shown below.
When you click on New Connection, you’ll be taken to a new tab to enter the API key which you created as parameter in the initial setup of this Connector. See #7 above. Enter the API key you have which works for this hosted app and then click Create connection.
Next, in case the Connection doesn’t appear, click Refresh button once.
Once you refresh, you should see your Connection come up and selected.
Now, next step is to test the Custom Connector itself. Enter the values that you wish to test for and click Test operation.
You’ll see the test results based on what the hosted code is supposed to perform.
In my case, it was easy as it just greets the name entered.

And your Custom Connector is now ready to be used!

Consuming Custom Connector

Now, let’s see how you can use the Customer Connector in Power Automate in order to perform the operation in your Flows –

Once in Power Automate, look for the Custom tab in the Action selector.
Then, you can see the Action you defined in your Connector Definition steps above.
Since you need to authenticate using the API key you have, the create Connection step will ask you this info and you can give the name of the Connection.
Pass the value you want to pass as data.
Finally, you can just save and test the Flow itself and look for your Outputs.

And that’s how you can have a Custom Connector for your custom app/service your have created. I’ll soon write about other aspects of Custom Connector which I wasn’t able to cover in this blog.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

HTTP Trigger Azure Function Authorization Types simplified

July 14, 2024July 14, 2024 priyeshwagh777 Azure Functions, Microsoft Azure azure, cloud, power apps, Power Automate, Power Platform

Now, many of you must be wondering how the Authorization types for Azure Functions using HTTP Triggers work and where to look for information while using these different types. Hopefully, this post helps simplify each of those for you.

Now, when you create a new Azure Function from Visual Studio or from the Azure Portal, you’ll be asked about Authorization where you’ll find the selection to either be 1 of the below –

Anonymous
Function
Admin
System

Anonymous

This type of Authotization let’s you use the Azure Function without needing for any key and anyone with the URL alone can access it. Of course, this is not recommended for any production use –

Now, if you notice your Visual Studio, when you write your first Azure Function, it comes with pre-defined method ready for you to continue to write your own code. But right away, you’ll see that the Authorization method is pre-defined considering you must’ve selected Anonymous while starting the Project.
Also, since the Azure Function is understood to be Published already on the Azure Portal, you’ll see in the Function’s settings that the same has been reflected as well.
Now, if you test this using Postman, the code will be able to run directly just using the URL without any API key. Either you pass in the body – and you’ll get a 200 OK with the result that the Azure Function is supposed to result.

Or using query parameters – the result will be the same.

This simply explains Anonymous authorization. Without any check on who’s supposed to access the Azure Function.

Function

In this type of Authentication, only the Function and resources associated to it will be accessible. This needs the caller to have a key [or code] to be passed while calling Azure Function –

Let’s look at the code, and see that the type is not set to Function for Authorization.
And when you Publish the code, the same will be reflected in the Settings too.
And when you want to access the Azure Function from Postman, you’ll need the Function Keys defined in the Function Keys area of the Function itself – a Default Key is given already but you can choose to add your own keys and using any of them would do.
Now, here’s what the Key looks like when you click on Show [there’s a button on the far right to expose the key’s value]
Now, when you go to Postman, you need to can pass this as a query parameter –

Now, let’s look at the Admin Type of Authorization.

Admin

In this type of Authorization, you get access to Functions’ Runtime APIs. The way to use the Admin key is similar to the Function Keys, just that they are available from the Function App itself than the Function –

Now, when the Authorization is set to Admin
You’ll see this reflected in the portal once Published.
Now, in the Function App itself – you can navigate to the App keys under Functions [as of the portal’s layout in mid-2024]
You can expose to see this value and share it to the clients who are going to consume this Function App. They key required here is the _master
Now, you can test this using Postman

Remember, this type of Authorization is to be used when the calling client needs to also access Functions Runtime API.
Finally, Let’s look at the System type.

System

This type of key is managed by Function runtime and is used when the calling client when there’s a need for granular access to function runtime features.

Now, you can set this from the code and publish it.
And it’ll appear in the settings of the Function [In case when the Function wants to access granular function runtime features].
And this is present in the App keys area under System Keys section.
And when you test the same, they work just like any other key from the Function app when called.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Lock fields on Editable Grid using JavaScript in Dynamics 365 CRM

June 11, 2024 priyeshwagh777 D365 WebAPI / JavaScript Dataverse, Dynamics 365, dynamics 365 crm javascript, editable grid, lock fields on editable grid, power apps, Power Automate, Power Platform

At times, you use Editable Grid and by default – all the fields which are editable by the system are exposed and can be edited if they are present on the Editable Sub-grid. You might not want to allow all fields to be editable on the Editable Grid – so here’s how you can lock selected fields on the Editable Grid using JavaScript.

Use Case

Let’s look at the below example where by default, the fields are Editable because you are using an Editable Grid –

You might want to lock the Status field since it shouldn’t be something end user should be able to change by themselves.
So in such scenarios, you might want to keep most fields open but lock some of them on the Editable Grid itself. Let’s see how we can do it using JavaScript

JavaScript Code

Here’s a sample code which you can use to loop through all the fields you want to lock on the Editable Grid –

Code within a class – [You can just use the lockFields function separately too.]

oSubscriptionCustomization = { lockFields: function (executionContext) { var oFormContext = executionContext.getFormContext(); if (oFormContext) { var arrFields = ["cft301_status"]; var objEntity = oFormContext.data.entity; objEntity.attributes.forEach(function (attribute, i) { if (arrFields.indexOf(attribute.getName()) > -1) { let attributeToDisable = attribute.controls.get(0); attributeToDisable.setDisabled(true); } }) } } };
In the above code, I’m reading from an array called arrFields and all the fields listed in the array will be looped through and locked.
Once my JS file is ready, I can open the Editable Grid control itself on the parent form and then loop for Events tab to register my function on the grid.
In the Event tab, look for the UI Event called as OnRecordSelect
Here, you can register your function. Since, I’m using class too – I’ll use classname.functionName
Once done, save and publish your changes. Now, you’ll see that the field is locked when you select the record on the Editable Grid.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Update SVG Icon to Custom Entity in Sitemap | Model Driven Apps

April 2, 2024 priyeshwagh777 Power Platform Admin Center crm entity icon, custom entity in crm, Dataverse, Dynamics 365, power apps, Power Automate, Power Platform, Power Platform Admin Center, svg icon

So, if you are used to updating Icons to entities in the classic UI, here’s what you need to do in order to update the SVG image of a Custom Entity you just created using new Power Apps Maker portal.

Let’s see below is you custom entity and it comes with its default icon which you want to set to a custom SVG icon.

Adding SVG Icon to Custom Entity

Given that you have appropriate access to the be able to Customize the system, follow the below steps –

In your solution, you have the table as well as the SVG Icon you just created the Web Resource for and uploaded an image which you want to set as Icon.
Now, select the Table you want to set the SVG icon to, and click on Properties.
On the right hand pane, expand the Advanced area and look for the Choose table image field.
Then, start typing the Display Name of the SVG icon which you wish to set to this Entity.

Click Save if no other changes are to be done.
Once Saved, click on Publish.
Now, when you refresh the App where the custom entity is listed in the Sitemap, you’ll see the icon updated.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Preferred Solution in Dataverse | Power Platform Admin Center

April 1, 2024 priyeshwagh777 Dataverse, Power Platform Admin Center Dataverse, default solution, Dynamics 365, power apps, Power Automate, Power Platform, Power Platform Admin Center, preferred solution, solution components in power platform, unmanaged solutions

By default, everything goes inside a Default Solution if you are aware of the classic way of doing Customization in Dynamics 365 CRM. And this causes components to be lost in Default solution without knowing who created where and what was that.

Hence, to be able to collect all the components created outside of Solutions, Preferred Solution is a great way to automatically add components created outside Solution in a single solution to ensure accountability.

Let’s see how this works with help of this simple post!

Mark a Preferred Solution

Given you have appropriate rights like System Administrator or System Customizer, you can go to the Maker Portal (https://make.powerapps.com/), and follow the steps below –

In the Power Apps Maker Portal, when you navigate to Solutions – you’ll see a message saying ‘Set your preferred solution’ and on the right hand-side show that the Common Data Services Default Solution is already preferred [You’ll know this from Customizations option in classic UI].

And on the top, you’ll see button to Set preferred solution.
Now, when you select to set preferred solution, you’ll see all the unmanaged solutions you have.
Select the one you want to mark as Preferred for anything not directly added to a solution.
Then, you’ll see that Preferred Solution label has been applied for that Solution.
Now, even if you add anything directly from other areas like Tables and add a field (for example), it’ll end up having the Prefix of the Solution itself.
In this example, it’s add Field 2. The Prefix set for the Preferred Solution was “cf301“
And when you open the Preferred Solution itself, the component you created outside the solution will be added to the Preferred Solution automatically.
This way, it’s easy to not lose any customization in Default Solution and makes it easy for all the components which were created outside of the solution to be gathered in place when you want to investigate your environment!

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Use Monitor to debug Model-driven apps remotely | Power Platform

March 18, 2024 priyeshwagh777 Microsoft PowerApps, Power Platform Admin Center Dataverse, debug monitor, debug monitor model driven power apps, debug monitor power apps, Dynamics 365, monitor in model driven apps, monitor in power platform, power apps, Power Automate, Power Platform

Monitor is one feature that comes in super handy when end-users complain about an issue which is difficult to ask end users to send across logs from the browser.

And here’s where Monitor comes in handy!
Let’s see how this works through this simple blog post!!

Capture events from Monitor in Model Driven Apps

Here’s how you can Monitor in Model-driven apps’ Monitor to capture issues on an End User

You can go to Power Apps Maker Portal (https://make.powerapps.com/) and make sure you are switched to the intended environment.
Then, select Apps on the left hand pane and expose all the Apps. Select the Model-Driven app you want to enable Monitor for. Once you select, you can then drop down from Details flyout menu and click on Monitor.
Once you click on Monitor, it opens the Monitor application itself where all the logs you work on will be captured. And you can also notice that there’s a Play model-driven app button as well to enter in Debug mode.
It opens the Model-driven app in a new tab and asks you to confirm if you want to join the debug session.
Once you click on Join, it’ll run the app in debug mode and you can see the Monitor tab and notice that it has started capturing the logs based on your operations in the Model-driven app session you are running in parallel.
And when you go about working in the model-driven app, it’ll keep capturing the traffic just like on a browser’s Network in Dev Tools
Now I deliberately added an erroneous code in my custom JS so that I could capture an exception in the monitor.
And if you look at the monitor, you’ll see that this has been captured.
And this is the wrong script I entered so that my code wouldn’t find the incorrect field name and throw an error when I try to retrieve value from an attribute that doesn’t exist (without null checking if the attribute exists or not)
However, best use case is when you ask end-users to join your session. Let’s see in the next session on how you can achieve this.

Invite Users to your Debug session

In the Model-driven apps monitor, here’s how you can invite other users to join your session –

In the Monitor, you’ll see Invite or Connect to a User. For this example, I’ll choose Connect user option.
Then, I can simply search for the User whom I want to generate a join link for.
Now, once this user is added, you’ll see a copy link option to copy the link and pass it on to the user who needs to join.
Once the end user has this link, then can join the session and they’ll see this message on their Dynamics model-driven app
And similarly, once they start reproducing the issue, you can start capturing the traffic on your end.

Hope this was useful! In order to fully understand the capabilities of Monitor for model-driven apps, here’s Microsoft’s official documentation – https://learn.microsoft.com/en-us/power-apps/maker/monitor-collaborative-debugging?WT.mc_id=DX-MVP-5003911

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Why Environment Variables don’t appear in Flows? | [Quick Tip]

March 5, 2024 priyeshwagh777 Power Automate Dataverse, Dynamics 365, environment variables, environment variables in flow, power apps, Power Automate, Power Platform

At times, if you are new to working with Environment Variables and you’re looking to use them in your Flows but don’t see them?

Here’s why!

Flows Outside Solutions

If you are creating Flows from the My Flows section, let’s see if you can access Environment Variables or not –

If you use My Flows way to create your Flows as shown below –
You won’t be able to access Environment Variables in that Flow

Flows in Solutions [Default and other Solutions]

So, you’ll need to have your Flows inside a Solution – even if you are creating a Flow in Default Solution, you’ll be able to access Environment Variables from another solution –

If you are in a Default Solution as shown below and you create a Flow there, you’ll be able to access Environment Variables.
And you create a Flow there, you’ll be able to access Environment Variables.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Pre-Export Step Required setting in Deployment Pipeline | Power Platform Pipelines

March 5, 2024 priyeshwagh777 Power Platform, Power Platform Admin Center azure, Dataverse, devops, power apps, Power Automate, Power Platform, Power Platform Admin Center, power platform pipelines

Now that you must’ve already setup your basic Power Platform Pipeline as yet and are looking to explore how to extend the Power Platform Pipeline to do more advanced operations, this post is for you!
In case you are still looking to first setup your Power Platform Pipeline, you can check this Blog Series which this very post too, is a part of – Power Platform Pipelines | Blog Series

What is Pre-Export Step Required Setting?

This is the ability to have a trigger before an Export operation from the Development Environment is initiated in order to run the pipeline – only available for the first stage in the pipeline.

This is provided so that you may want to run some external operations before this is taken through the pipeline for deployment.

Use Case is – that you want to first seek an approval from the Admin before the Solution is deployed to Production (or rather, sent through the pipeline for deployment). Once approved, the pipeline should automatically proceed towards executing the rest of the deployment stages.

Pre-Export Step Required

While setting up your Pipeline, in case you were wondering what Pre-Export Step Required setting was, see below –

Once you mark this field as checked/Required, save the record and it’ll appear like this on the record.
What this does is, it runs the trigger action ‘OnDeploymentRequested’
And once this Flow is trigger based on this Action, you can perform custom logic to be carried out and be successful before the deployment is carried forward.
In this example, I’m setting a simple Approval process to be in place so that the Admin is aware and approves all the Deployment requests.
Now, once an Approval is received, you need to check the status of the request and if it’s Approved, you need to run Perform an unbound action to initiate the Action ‘UpdatePreExportStepStatus‘
You’ll need to pass the StageRunId – You’ll get this in the Dynamics Content Properties of the Flow itself from the trigger.
Then, you need to set the Status of 20 – this means Approved.
For rejection, the status to set is 30.
Now, once this Flow is in place, every time a Pipeline is Run to deploy the solution, it’ll first wait for the Approval process to complete and the pipeline itself will show the below message.
This status can also be seen in the Deployment Stages in the ‘Deployment Pipeline Configuration‘ app as well.
Now, the Admin on the other hand, will receive a Power Automate Approval like this (based on whatever you have configured). This is received on both Approvals in Teams and in Power Automate as well.
Once the Approver approves, I’ll enter some notes while approving.
The pipeline will then proceed to deploy to production.
And this will also proceed on the UI in Pipelines as well.
Once deployed, you’ll see that this is completed Successfully if there are no issues.
You can also see the History. The End Time will represent when it was completed as opposed to Start Time representing when the Deployment Request was initiated.
And also in the ‘Deployment Pipeline Configuration‘ app.

Here’s official Microsoft documentation on how you have Gated Extensions like these to be in place in Power Platform Pipelines – https://learn.microsoft.com/en-us/power-platform/alm/extend-pipelines#gated-extensions-available?WT.mc_id=DX-MVP-5003911

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

D365 Demystified

A closer look at Microsoft Dynamics 365.

power apps

Cards in Power Apps

Create a Card in Power Apps Maker Portal

Sending a Power Apps Card to Teams Chat

Like this:

Recycle Bin in Dynamics 365 CRM | [Preview]

Enable Recycle Bin

Deleted Records

Like this:

Create a Custom Connector For Power Automate & Power Apps

Use Case

Create Custom Connector in Power Apps / Power Automate

Consuming Custom Connector

Like this:

Lock fields on Editable Grid using JavaScript in Dynamics 365 CRM

Use Case

JavaScript Code

Like this:

Update SVG Icon to Custom Entity in Sitemap | Model Driven Apps

Adding SVG Icon to Custom Entity

Like this:

Preferred Solution in Dataverse | Power Platform Admin Center

Mark a Preferred Solution

Like this:

Use Monitor to debug Model-driven apps remotely | Power Platform

Capture events from Monitor in Model Driven Apps

Invite Users to your Debug session

Like this:

Why Environment Variables don’t appear in Flows? | [Quick Tip]

Flows Outside Solutions

Flows in Solutions [Default and other Solutions]

Like this:

Pre-Export Step Required setting in Deployment Pipeline | Power Platform Pipelines

What is Pre-Export Step Required Setting?

Use Case is – that you want to first seek an approval from the Admin before the Solution is deployed to Production (or rather, sent through the pipeline for deployment). Once approved, the pipeline should automatically proceed towards executing the rest of the deployment stages.

Pre-Export Step Required

Like this:

Create a Card in Power Apps Maker Portal

Sending a Power Apps Card to Teams Chat

Share this:

Like this:

Enable Recycle Bin

Deleted Records

Share this:

Like this:

Use Case

Create Custom Connector in Power Apps / Power Automate

Consuming Custom Connector

Share this:

Like this:

Anonymous

Function

Admin

System

Share this:

Like this:

Use Case

JavaScript Code

Share this:

Like this:

Adding SVG Icon to Custom Entity

Share this:

Like this:

Mark a Preferred Solution

Share this:

Like this:

Capture events from Monitor in Model Driven Apps

Invite Users to your Debug session

Share this:

Like this:

Flows Outside Solutions

Flows in Solutions [Default and other Solutions]

Share this:

Like this:

What is Pre-Export Step Required Setting?

Use Case is – that you want to first seek an approval from the Admin before the Solution is deployed to Production (or rather, sent through the pipeline for deployment). Once approved, the pipeline should automatically proceed towards executing the rest of the deployment stages.

Pre-Export Step Required

Share this:

Like this: