Create Dataverse Virtual Table from SharePoint List | Power Platform

June 6, 2023 priyeshwagh777 Power Platform Admin Center connect to external data source, power apps tables, Power Platform Admin Center, virtual table in dataverse

Now, you can create a Dataverse virtual table by referencing a SharePoint List. This is an easy way to bring in schema from your SharePoint List in use and make it into a Dataverse Table.

Good news is that this also syncs back to the SharePoint List! Let’s see how.

SharePoint List

Let’s say you have a SharePoint List which you want to convert into a Dataverse Table in your Power Platform –

Let’s do this by creating using a Virtual Table which now connects to SharePoint and SQL. Please note that at the time of writing this post, connecting to external data is still in Preview.

Create Table

Here’s how you can create a virtual Table in Power Apps Maker (https://make.powerapps.com) –

Once you are in Power Apps Maker, go to Tables and you can drop down from Create Table menu.
You’ll see and option to Create by connecting to external source.
Now, you have 2 options at this point of writing this blog. One is SQL and other is SharePoint. We’ll select SharePoint for this example. Both also use the connection you are logged in.
Once you select SharePoint, you’ll either be asked to select one of the recently used Sites or if you know the URL of the Site in which your list resides, you can choose the same.
Refer below that I’m choosing up to the name of the Sub-site in question.
So, you can either select a recently used Site or just paste the URL of the Site which has your List in it.

OR
Once you are in the desired Site, you’ll see the List under that Site.
Once I select the List, I’ll be asked if I need to change any schema name from the ones identified by the wizard.
Or if everything looks OK, you can simply click on Next. You’ll be given a summary of what Table will be created from your SharePoint list.
It takes a few moments to create this Virtual Table for you with the data from the SharePoint List.
Once ready, it’ll appear as below with the data and you can start adding your data as well.
Also, the data you add from the Virtual Table is also sent back to the SharePoint List.
This entity / table will be listed as any other Table in the Power Apps Maker with the Virtual type.

Hope this helps!

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

Thank you!

Environment Assignment settings in Power Platform Admin Center

May 23, 2023 priyeshwagh777 Power Platform Admin Center environment create permissions, environment maker, Power Platform Admin Center

Environment Assignments and who should be able to create what types of Dynamics 365 CRM / CE / Dataverse environments can now be easily controlled.

You can either let everyone create a certain Type of environment or only enable Admin groups to create environments in Power Platform Admin Center! Let’s see how.

Restricting Users from Creating Environments

You can now restrict which types of Environments are allowed to be created for the type of audience in your tenant –

If you are one of the Global Admins, Power Platform Admins, you have access to the Power Platform Admin Center settings (https://admin.powerplatform.microsoft.com/tenantsettings)
And you’ll see the below types of Environment Assignments available for you to tweak
Developer environment
Production environment
Trial environment
Add-on capacity
And in this example, let review and modify the settings for Production types of instances and who should be able to create this environments.
Every type of assignment will have the below 2 options –
Everyone
Only specific admins (Global Admins, Power Platform Service Admins & Delegated Admins)
Reference Link: https://learn.microsoft.com/en-gb/power-platform/admin/control-environment-creation?WT.mc_id=ppac_inproduct_settings?WT.mc_id=DX-MVP-5003911
Once your preferences are set, just click on Save and the settings will be applied. Let’s see in the next section how this works.

Restriction Imposed

Here’s how a User will be restricted when they try to create the Types of environments when they are not part of the Admin Groups –

Although, every user will get an option to Create using the Create button and select a Type of environment. When a User selects a Type, in this case Production
And when they click Next, and enter further details in order to create the environment, they’ll see this error message.
And to validate, you can look at the Roles in Microsoft 365 Admin Center under Users as to what Roles they have been assigned with.

Hope this helps!

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

Exchange Online Mailbox License Error | Exception Missing Exchange License

May 11, 2023 priyeshwagh777 Office 365 Administration Exchange Online, microsoft exchange online, no mailbox exception

In case you are setting up your M365 and setting up Exchange Online in the process, your Email URL is: https://outlook.office365.com/mail/

But, you see the below error which reads as

err: Microsoft.Exchange.Clients.Owa2.Server.Core.OwaUserHasNoMailboxAndNoLicenseAssignedException

No License Exception

Here’s why you see the Exception.

If you open the User record in the Microsoft 365 Admin Portal, you’ll see that Microsoft Exchange Service is not seen in the list of Services.
Now, let’s procure a trial for Exchange Online or any of the E3 / E5 plans which you plan to purchase based on your requirements. They have Exchange Online services available which will enable your Exchange Online mailbox.
In this example, I’ll start a trial because I don’t want to buy for Enterprise purposes for the sake of this example.
Now, once I started this trail. And if you see the comparison chart above, you could even opt for other licenses that offer Exchange Online – say, Office 365 E3
Now, I can see that this license is available for me to assign to the user.
And when I select the above license, I will see the Service available in the list as well.
Save your licensing changes / preferences and let 5-10 mins pass for the services to be applied to the User.
And once you reload/refresh the Outlook web app, your mailbox will be available or retained (if it was expired on an existing license.)

Hope this helps!

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

See which form is displayed in Dynamics 365 CRM | [Quick Tip]

April 26, 2023 priyeshwagh777 Dynamics 365 CE dynamics 365 crm form name, dynamics 365 form order, fallback form

At times, it is not clear which form is displayed when looking at a record.

It may seem like Account form is displayed based on what the label says but things could be different.

And you assume it is this form that is being displayed.

But, this is now always the case. So, let me explain!

See Form Name

Here’s how you can see the true form name –

Hover on the tab where Dynamics 365 CRM is opened.
You’ll see the actual form that is being displayed even if the name under the record Name is shown as “Account”. In this case, it’s the entity name.
Here, the form name displayed is “Account for Interactive Experience”

When does this happen?

This happens if there are no other forms in the App you are using which have been enabled for your Security Role.
And then there’s no other form left for you to see.

Fallback Form?

The fallback form will take into effect if no other form is enabled for your security role. In my example, the form “Account for Interactive Experience” was in fact enabled for my Security Role and hence, I didn’t see the default “Account” form even though it was ranked higher in the Form Sequence.

Hope this helps!

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

PSA to PO Upgrade Errors | Resolve by reviewing Upgrade Logs

April 24, 2023 priyeshwagh777 Project Operations project operations upgrade, psa to po, psa to project operations

Since you and your Org are preparing to upgrade from PSA v3 to Project Operations given that you are covered in terms of what licensing you need, the first step is to try upgrading your environments to PO.

This upgrade operations needs to ensure you have clean data in your environment before you could upgrade. Hence, these validations will cause failure in upgrading the PSA on the selected environment.

Let’s see what needs to be done to identify and rectify the failures.

Upgrade Failure

Typically, you’ll see below failure if you are trying to upgrade from PSA to PO in the Power Platform Admin Center –

You’ll see that the installation has failed.
Now you can directly go in Project Service.

Error Logs in Project Service

Now, in Project Service, you can do the below –

You can see the Upgrade Logs and sort the Started field by Descending to make the latest one appear on top.
You’ll notice a Failure status entry.
When you open it up, it’ll have the details. You’ll see the upgrade entry as shown below. You need to open it.
Once you open this Upgrade Version record as shown above, you’ll need to sort the Steps as shown below to show all the Failure status records first.
Once you open one of the failed ones, you’ll be able to see why the upgrade failed on the Upgrade Step record.

These error messages are self-explanatory and you should be able to take corrective action by going through them and working to resolve given you have functional knowledge of Dynamics 365 PSA/CRM.
As you resolve the issues as you find them, you should eventually get to upgrading the Project Operations successfully once all data dependent validation issues are resolved.

Hope this helps!

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

Get the New Teams client for your organization | Teams Admin Center

April 4, 2023 priyeshwagh777 microsoft 365, Microsoft Teams, Office 365 Administration Microsoft Teams, New Teams

Here’s how you can enable Users to choose to update to the new Teams if you are a Teams Administrator in M365 Admin Center

So since you are using the current (or old) Teams version,and the option to enable New Teams is not avilable to you, you would see no option to update in this Title Bar of the Teams app itself.

Let’s see how we can enable Teams for the Users organization-wide.

Enable Org-Wide New Teams Update

If you are the M365 Admin / Teams Administrator in your organization, here’s how you can enable the new Teams switch for the users –

Look for Teams in the Admin Centers area.
Once in Teams Admin Center, you can look for Teams Update Policy section.
Given that you don’t want to create a new policy but want to apply this setting Org-wide, you can open the Global policy which is already present by default.
Once you open this policy, you’ll find the Use new Teams client option and choose Users can choose option.
Once sure, click on Apply. And you’ll be asked for Confirm.
Once you are confirmed, that’s it.

New Teams

Now, here’s how you ensure you are getting the new Teams.

Once you know the Admin has enabled the new Teams for your organization, sign out from Teams.
Now, when you login again, you can see the button appear for you.
Once you click the switch, you’ll get the Get it now button.
If you click on See the full list, here’s the Documentation for the same – https://adoption.microsoft.com/en-us/new-microsoft-teams/
You’ll see the new Tems app show up.
Please note that if you are also part of other organizations, your other orgs will also show up in the same new Teams client.

Hope this helps!

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

Perform a changeset request in Dataverse connector in Power Automate

April 3, 2023 priyeshwagh777 Dataverse, Power Automate Dataverse, perform a changeset request dataverse, perform a dataverse connector, Power Automate

You must’ve noticed Perform a changeset request in the Dataverse connector in Power Automate.

Purpose of this Action is to perform batch of available Dataverse connector actions successfully or rollback the batch performed inside this changeset request.

Here’s what it does.

Perform a changeset request

Here’s how to use the connector action

Select Perform a changeset request in the Dataverse connector Actions list.
Now, since this works like a batch of operations to perform all actions successfully or “rollback” operations, you’ll see this working like a Scope but only for Dataverse actions.
You have the below Actions available to perform.
Now, let’s design an example changeset batch here.
First, I’ll create an Account and then a Contact.
When this Flow runs, for example, if the Contact creation fails, the Account creation too will be rollbacked unlike having these steps outside of the “Perform a changeset request” action.
Please note that the Outputs of the Changeset request itself or even within the steps within a changeset request cannot be captured or referred to in Dynamic Content.

Hope this helps!

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

Migrate Flow to latest Microsoft Dataverse connector

March 31, 2023 priyeshwagh777 Power Automate dataverse connector, migrate flow, migrate to the new dataverse connector, power automate dataverse connector

If you are using the legacy Dataverse connector which has the gray logo and looks like the below.

You can run Flow checker to identify if Power Automate can help you migrate the Flow to utilize the latest connector.

Flow checker message

Here’s what the old Flow looks like –

You would see the below message once Flow Checker suggests you changes –
Once you click on the “Open the migration assistant” link on the suggestion, it’ll pop-up a window to ask if you are ready to allow Migrating the Flow to the latest Dataverse connector.
Once you click on Migrate, it’ll start the migration process and based on how lengthy your flow is – in a few moments your new Flow will be ready.
So, once the migration is completed, you’ll see a message like this.
Once you click on Open the new flow, you’ll notice that the new Flow now has (Migrated) written in.
And once you click on Edit, you’ll see that the Flow step where old Dataverse connector was used has been replaced by the new Connector

Hope this helps!

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

Resolve Project Operation errors | PSS Error Logs

March 27, 2023 priyeshwagh777 Project Operations Project Operations, pss error logs

In case you are new to Project Operations or have recently upgraded from Project Service Automation to Project Operations, and if you are running into some issues, here’s how to identify them

Error

Here’s an example error –

Let’s say you are trying to add Tasks to the Schedule in Project Operations, and you see the below error in a few moments.
Now, if you look at the above error in red, it won’t let you know exactly is the issue. Hence, here’s how you find it. Check the next section.

PSS Error Log

Here’ s how you can get to where the error is –

You can look for the issue in the below section –
Go to Settings in the Project Operations App.
Then, go to the PSS error logs and you’ll find an entry there.
And once you open it up, you’ll find the issue there. There could be different issues based on what operations you are trying to perform in Project Operations.

Now, based on your knowledge of Error Resolution in Dynamics 365 CRM application, you can work towards solving your errors.

Hope this helps!

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

Identify deprecated JS code in your Power Platform solution using Solution Checker

March 15, 2023 priyeshwagh777 Power Platform, Power Platform Admin Center deprecated javascript, odata v2, solution checker, solution in power platform

Recently, you must’ve received an intimation from Microsoft saying that ODATA v2 is now deprecated. See this link: https://powerapps.microsoft.com/en-us/blog/odata-v2-0-service-removal-date-announcement/

And if you are wondering how to go about finding what has been used, you can use Solution Checker to identify deprecated code which should show up like below using your Solution Checker.

Let’s see how we can use Solution Checker!

Running Solution Checker

Here’s how you can run Solution Checker in Power Apps Maker Portal (https://make.powerapps.com/) and see the results –

Given that your solution already contains the JS Web Resources which you want to run Solution Checker on, you can select the Solution and expand Solution Checker to click Run as shown below.
It takes a few moments to Run the Solution Checker solution. You’ll see the spinner as shown below.
Once completed, you can expand the Solution checker and click on View Results.
Once you click on View Results, you’ll see the list of detected anomalies in your JS Web Resources.
Apart from the suggested JS best practices, you can see the Category Upgrade Readiness to identify the deprecated code being used in your solutions.
Once you click on the Reference link in each of these results, it’ll open up a Pane on the right hand side to show what the issue is
And when you click on Get the complete guide, here’s the link of the same (https://learn.microsoft.com/en-gb/power-apps/maker/data-platform/powerapps-checker/rules/web/avoid-2011-api?WT.mc_id=DX-MVP-5003911) which will give you the below details in Microsoft Learn Documentation –
Now, if you look at the code that is being references in the Solution Checker result, you’ll see the old code (marked with Red Box)being used.
Instead, you should use the new code (marked with Green Box) to do carry out the newer version of the functionality –
See the next section in this blog to get the details on the deprecation in client side scripting for Power Platform / Dynamics 365 CRM.

Important Deprecations for Power Apps & Power Automate

Here’ are the Deprecated APIs for Power Platform / Dynamics 365 CRM Client Scripting: https://learn.microsoft.com/en-us/power-platform/important-changes-coming#some-client-apis-are-deprecated?WT.mc_id=DX-MVP-5003911

Hope this helps!

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

D365 Demystified

A closer look at Microsoft Dynamics 365.

Create Dataverse Virtual Table from SharePoint List | Power Platform

SharePoint List

Create Table

Like this:

Environment Assignment settings in Power Platform Admin Center

Restricting Users from Creating Environments

Restriction Imposed

Like this:

Exchange Online Mailbox License Error | Exception Missing Exchange License

No License Exception

Like this:

See which form is displayed in Dynamics 365 CRM | [Quick Tip]

See Form Name

When does this happen?

Fallback Form?

Like this:

PSA to PO Upgrade Errors | Resolve by reviewing Upgrade Logs

Upgrade Failure

Error Logs in Project Service

Like this:

Get the New Teams client for your organization | Teams Admin Center

Enable Org-Wide New Teams Update

New Teams

Like this:

Perform a changeset request in Dataverse connector in Power Automate

Perform a changeset request

Like this:

Migrate Flow to latest Microsoft Dataverse connector

Flow checker message

Like this:

Resolve Project Operation errors | PSS Error Logs

Error

PSS Error Log

Like this:

Identify deprecated JS code in your Power Platform solution using Solution Checker

Running Solution Checker

Important Deprecations for Power Apps & Power Automate

Like this:

SharePoint List

Create Table

Share this:

Like this:

Restricting Users from Creating Environments

Restriction Imposed

Share this:

Like this:

No License Exception

Share this:

Like this:

See Form Name

When does this happen?

Fallback Form?

Share this:

Like this:

Upgrade Failure

Error Logs in Project Service

Share this:

Like this:

Enable Org-Wide New Teams Update

New Teams

Share this:

Like this:

Perform a changeset request

Share this:

Like this:

Flow checker message

Share this:

Like this:

Error

PSS Error Log

Share this:

Like this:

Running Solution Checker

Important Deprecations for Power Apps & Power Automate

Share this:

Like this: