Permissions in Project in Project Operations

By default so far, Users added to the Project have full access if not controlled using Security Role. So here’s a simple tweak to restrict some users from having full access on Projects!

Enable Permissions in Projects

Given that you have correct Sys Admin rights in Project Operations, here’s how you can enable Permissions on a Project –

  1. Navigate to the Settings area in Project Operations.


  2. Look for Feature Control in the ribbon and drop down, you’ll see Permissions on Project control.

  3. When you turn this one, note that it cannot be turned off later. And this is a System User level change.
    Also, here’s the link mentioned in the message: https://learn.microsoft.com/en-us/dynamics365/project-operations/project-management/access-control-on-task-grid?WT.mc_id=DX-MVP-5003911

Permissions Settings

Now, in a Project, you can navigate to any System User and see the below –

  1. Navigating to this user, I can see the below option in the ribbon button.

  2. And I see only 2 options – Full or Read-only.
    By default, they are all selected for Full permissions. So this setting gives you option to set as Read-Only on the Project.

This was a small tweak but useful if you want to be careful with too many resources having access to the project for editing where shouldn’t have to from the permissions/security role standpoint.

Thank you!

Setting up Codex with Power Platform MCP Server

Amongst available AI clients available, Codex is well-known by ChatGPT and here’s how you can use to configure with Power Platform MCP Server.

Install Codex on VS Code

One of the first things to do is to install Codex as an extension in Visual Studio Code –

  1. Look for the below extension and you should see a ChatGPT icon.

  2. Once this is installed, go to Extensions and you can sign in with your GitHub Pro account.

  3. It’ll open up a Sign-in page and you’ll need to enter your credentials.

  4. Make sure you open a Folder in VS Code and also ensure npm is installed by running this command in terminal ‘npm -v‘.


  5. Next, before you configure the TOML file – make sure you are having powerplatform-mcp installed locally and then configure the TOML file for Codex.

Downloading Power Platform MCP locally and connecting to the MCP

Now that Codex is installed and NPM is installed as well. Let’s first download Power Platform MCP first and then connect it to the Power Platform MCP environment –

  1. Let’s check if PowerPlatform-MCP is already installed or not by checking its version number.
    Below, it says that it didn’t find zsh, means powerplatform-mcp is not installed locally.

  2. Because I use a Mac, I can do so using Homebrew. You can check alternatively on doing this using Windows and downloading using Powershell.
    In case you face permission issues on the device, you can just run the below command –
    sudo npm install -g powerplatform-mcp” and you should see the packages getting downloaded successfully.

  3. Now, go ahead and configure the Toml file.

  4. Then, in the TOML file, you can enter the configuration like so –

  5. And when you try to query in Codex, you’ll see the results come through in the form of answers.

Hope this was useful!

Thank you!

Finding Indexed Columns in Dataverse Search

In recent times, you must be seeing Indexed Search in Dataverse. Here’s how to make sure you can configure those.

Indexed Search

Given the right permissions, you can go to Power Platform Admin Center (https://make.powerapps.com/) –

  1. Open Solutions, you then be able to scroll down to Default solutions –

  2. Once you open Default Solution, or any other Solution which has tables whose tables you want to index. Click on Overview and then you’ll see Dataverse search on the right hand side.

  3. And when you view to the right, you’ll see a button called ‘Manage search index

  4. And when you click on Manage search index, you’ll see list of tables enabled for Search.

  5. And when it says the no. of columns added, they can be seen from the Quick Find View.


  6. And you’ll see the columns selected to be found.


This will then result in the Search being reflected based on the Find columns shown here.

Thank you!

Allocate Storage Capacity for Dataverse environments | Power Platform Admin Center

As Dynamics 365 storage capacity is expensive and need to meticulously manage the same is of prime importance, Microsoft is providing a way to allocate the storage capacity amongst the Dataverse environments.

So, here’s a way to allocate capacity between Database, File and Log types for each Dataverse environment and get take corrective actions when the capacity is reached.

Manage Capacity

Given you have correct rights in the Power Platform Admin Center, you’ll be able to see the Capacity under Resources –

  1. On the left hand menu in Power Platform Admin Center, look for Resources as shown below –



  2. When you see the list of all the environments, select any one to see the option to go to the Storage Allocation page as shown below.

  3. Once you are in this page, you’ll see the total consumption of Database, Log and File types across all environments – and you’ll see the button to manage this capacity amongst the environments.

  4. Now, when I click the Manage Capacity button, I’ll see a list of the environments and whether they are already within capacity or not. I can then select the environment which want to allocate/review the allocated capacity for –

  5. When I select the environment here, I’ll see that by default nothing has been allocated under this new model – but I can then enter thresholds for each type within the available space and not less than what is already consumed.

    By default, the values are blank.

  6. Now, since I have some numbers and made sure to draw from the available capacity if the thresholds are exceeded, I’ll click save for the consumption meters to show up indicating that the allocation is now saved.

This way, you can keep the environment consumption in check and make other environments take up the unallocated space and take corrective actions.

Best is to keep less used sandbox environments consume lesser space.

Hope this was useful!

Thank you!

Catalog in Power Platform

Catalogs in Power Platform are a way to distribute managed/unmanaged customization which ready install and extend on other environments. At the time of writing this post, the feature is in Preview.

Get Catalog Manager

Here’s how you can install Catalog Manager from App Source and onto your target environment –

  1. Go to the URL – https://appsource.microsoft.com/en-us/product/dynamics-365/powerappssvc.catalogmanager-preview?flightCodes=dde212e5c66047c59bf2b346c419cef6
    It’ll open in App Source as it’s not directly available from Install Apps in Power Platform Dataverse environments.
    You’ll see this App Source page –

  2. Once you click on Get it now, you’ll need to sign in using the Dynamics 365 Administrator privileges.

  3. Once you sign in successfully, you’ll need to click on Get it now again as shown below.

  4. Then, you’ll be taken to the page shown below where you’ll need to select the environment you want to install the Catalog Manager on. This will be the environment from where you’ll create your Catalog to be available to other environments.

  5. Once you confirm as shown below, Installation process will start like any other Dynamics 365 App.


    And then let it install for a few moments –


    And it’ll complete its installation in about 10 minutes.


  6. Now, once this is installed, check for the security roles available for users to be assigned with.

    Assign these roles to the Users who need to be either of them – below are the details on what the roles do.

Working with Catalog Manager

Now that Catalog Manager is installed, here’s how you can work through it –

  1. In your Apps, you should be able to see the Catalog Manager as well.

  2. Play the App, and in the App, you’ll see the Catalog Publishers table. This is where you have to create a Publisher and add Users from the Publisher for different roles.


  3. Here’s the sample Publisher I created and added the Admin User as a Publisher user as well.

  4. Once this is done, you are all set. Let’s move to the next section.

Create Catalog

Now, let’s look at the process of creating Catalogs which other environments in your Org can browse through and use –

  1. Let’s say you have a Solution which is supposedly a Catalog candidate which others can borrow and install.
    It has a mix of components which are categorized as usable in a Catalog.


  2. Here, you can select the Solution itself and click on Publish to Catalog (Preview) using the button as shown –

  3. Once you click on the Catalog, a dialog will open which you can select as Default

  4. Once you select the Default Catalog Name, you’ll be able to select if the components should be Managed components or unmanaged (as Templates).
    Then, I can choose to not select anything as a Primary Component to keep it simple.

  5. Now, I’ll enter the details as shown below which are self-explanatory.
    Published/Active Publisher will appear from the list and I can fill in the rest of the details which are applicable.

  6. Now, when I click Next, I can enter what the picture/icon should be –

  7. Finally, this is the summary and I can click Submit once done.

  8. Once everything looks good, this will be completed and show success.

  9. Now, since the Catalog is already set to auto-approval, it’ll appear in Catalogs –


Installing from Catalog

Now, as the Catalog is ready to be published, other environments can go in Catalogs and Get it from there in their current environments –

  1. For example, in this environment – I can see it in Catalogs and choose to Get it.

  2. Click Get to start installing.

  3. It’ll start installing.

  4. Once done, you’ll see that it has finished installing.

  5. And when you see the Solutions, since this was a Managed catalog – it’ll get installed as a Managed Solution in the selected environment.

  6. And the Components inside it will be managed too as expected.

Install History

As other Admins/Makers install from Catalog, you’ll see the Install History of the Catalogs in the Catalog Manager App –

  1. Under Install History, you’ll see the details as below –

Here’s Microsoft Documentation on the same – https://learn.microsoft.com/en-us/power-apps/maker/data-platform/catalog-overview?WT.mc_id=DX-MVP-5003911

Hope this was useful!

Thank you!

Setup Power Platform CLI using Windows installer [.msi]

In the past, I had posted about how you can use Microsoft Power Platform CLI from Visual Studio Code – Set up Power Platform Tools in Visual Studio Code | Power Platform CLI.

In this post, I’ll show how you can do so using direct download and installation using .msi file.

Download Power Platform CLI installer

Here’s the link you need to go to in order to download Power Platform CLI –

  1. Visit – https://learn.microsoft.com/en-us/power-platform/developer/howto/install-cli-msi?WT.mc_id=DX-MVP-5003911


  2. Once downloaded, make sure to start the installer, it’ll ask you for confirmation.

  3. It takes a few minutes to complete setting up. Then, you can Run powershell

  4. In PowerShell, you can type pac and enter to see if Power Platform CLI was installed. By default, it’ll connect to the organization your PC is connected to.

  5. Once connected, you’ll see list of commands for the CLI which you can use given you have the appropriate connections.

Hope this was useful!

Thank you!

Environment Routing in Power Platform Admin Center

In case you already have created Environment Groups, you can set some rules to divert how environments are created to Environment Groups.

If not, you might want to first take a look at a post on Environment Groups in Power Platform Admin Center!

Environment Routing is feature to redirect existing/new Makers to their own Developer environment when logging into the Maker Portal (https://make.powerapps.com/)

Routing in Environment Groups

Here’s how you can set Routing rules in Environment Groups in Power Platform Admin Center –

  1. Given that you have the correct Dynamics 365 Administrator privileges, you should be able to see the Environment Groups section and also see button to set the Environment Routing.

  2. In Environment Routing, you can choose to enable to Create personal developer environments for makers option.

  3. When you turn it on, you can choose to enable it either for All makers or for new makers only. I’ll enable it for All makers for this example.


  4. Now, I’ll select the Environment Group where the routing should happen to – for this, I’ve created a CFT Developers Environment Group.


    And Save.

Routing to Developer Environments

Let’s consider this example to demonstrate how Routing will work –

  1. When a developer logs into the Maker Portal (https://make.powerapps.com/), a setup will load for a few moments the user, let’s say, Amit Prajapati in this example, will be redirected to his own Portal –

  2. And if you look at the list of the Environments in the Group you selected for Routing, you’ll see that Amit’s Environment is now created.

  3. Now, another User Ethan Rebello also logs into the Maker Portal. He too will be redirected to his own environment.
    And the same will be added to the Group as well.


    Every developer will have access to only their own Developer environments and other’s won’t be able to access them.

Hope this was useful!

Thank you!

Environment Groups in Power Platform Admin Center

Environment Groups is a feature to let you club the environments of your choice together in order to govern them commonly and easily with Rules for the environments.

The Rules as of now which you can govern commonly for the grouped Environments are –

  1. Sharing controls for Canvas Apps
  2. Usage Insights
  3. Maker welcome content
  4. Solution checker enforcement
  5. Backup retention
  6. Enable AI-generated descriptions (preview)

    Let’s see how you can do this!

Environment Groups

Here’s how you can use Environment Groups in Power Platform Admin Center given that you have the correct Dynamics 365 Admin privileges –

  1. You’ll see in the Power Platform Admin Center that Environment Groups is its own section.

  2. Here, can you can click on Create a group as the button suggests and It’ll let you create a Group.

  3. Next obvious step is to simply give it a Name and Description.

  4. Once done, you’ll be able to select Environments to be added to the Group you just created.

  5. Then, select the ones which are relevant to be added to this group. Once done selecting, click on Add environments.

  6. Next, you’ll need to turn on the Managed Environment Modes for the selected environments. If all selected already have Managed Environments feature turned on, then they’ll simply be added further. In order to understand Managed Environments feature, you can refer to this post – Enable Managed Environments in Power Platform Admin Center


  7. It takes a few moments to turn on Managed Environments, then you can finally click on Add Environments to add them to the Group.
    As you see in the notification area, it takes a few moments to add the environments.

  8. Once the processing has been completed on the backend, the environments will be added.

Rules for Environment Groups

Now, let’s see how you can commonly set Rules for the environments in the Environment Group –

  1. You’ll see the tab called as Rules. Once your environments are added, you can go to this tab to look at the Rules you can change and apply.

  2. You’ll see that by default, the rules remain as is and are not commonly applied. Let’s modify Backup Retention rule at first.
    Once you select a Rule, you’ll get to Edit it.

  3. Once you Edit, for example, Backup Retention – you’ll see the default values which you can change in order to commonly apply to the environments in the Environment Group.

  4. Now, I’ll change it to 21 Days, as an example. Then, click Save.

  5. Let me change another rule.

  6. Now, you’ll see that the changed Rules will have star mark on it and are marked as bold.

  7. Now, when you click Publish, it takes a few moments for the Rules to be published and you’ll see the last published rules once applied.


    And here’s the latest status once changed.

In order to fully understand the capabilities and limitations of the Environment Groups, follow this Microsoft article on the same – https://learn.microsoft.com/en-us/power-platform/admin/environment-groups?WT.mc_id=DX-MVP-5003911

Hope this was useful!

Thank you!

Recycle Bin in Dynamics 365 CRM | [Preview]

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 –

  1. Go to the Environment’s Settings in Power Platform Admin Center (https://admin.powerplatform.microsoft.com/)

  2. Now, expand Product section and go to the Features option.

  3. 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.

  4. 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.

  5. 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 –

  1. For example, this is the Account record you want to delete.

  2. Go to the View Deleted Records section in the in your environment’s Settings area.

  3. You’ll see the Deleted records which you can select and choose to Restore.


  4. Confirm.

  5. 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!

Thank you!

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

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 –

  1. 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.

  2. Now, select the Table you want to set the SVG icon to, and click on Properties.

  3. On the right hand pane, expand the Advanced area and look for the Choose table image field.


  4. 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.

  5. Once Saved, click on Publish.

  6. 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!

Thank you!