While trying to set the Start Location / End location to the Resource Address for Bookable Resource, we might get the below error
Exception Message: The latitude or longitude for the User record associated with this resource is invalid. Please provide a valid latitude and longitude and then set the start and end location for this resource again.
Here as the error message specifies we need to specify the latitude and longitude value for the corresponding resource type record associated with the Bookable Resource.
In the case of Contact, we can use the Geo Code option, and specify the address to populate the Latitude and Longitude details.
In the case of a User record we do not see the Geo Code option so there we can manually specify the values for it.
Now we will be able to update the Start / End Location as Resource Address in our Bookable Resource record, without getting any error.
Recently in one of our flow triggers – When a row is modified (Dataverse), we got the below error
Exception parsing _msdyn_billingaccount_value eq ‘a84c5028-ecdf-ed11-a7c7-00224893b2b0’ submitted for attribute filterexpression of callback registration. Target entity: msdyn_workorder. Exception: Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’.
This is because we were using single quotes around the GUID value in the Filter rows property.
We need to remove the single quotes around the GUID
GUIDs are considered a primitive data type in OData and should be represented as raw values without quotes. By removing the single quotes, we’ll ensure that the GUID is treated as a valid identifier in our filter condition.
While trying to create a Website with Template – Partner Portal,
we observed the provisioning stuck at – Getting set up…
Also, it was showing the below error on checking the Site Health.
“URL of the Dynamics 365 organization connected to this portal has been changed.” Which wasn’t the case as the URL of the organization was correct.
Usually, the 1st Web Site takes time around an hour and then any new website is provisioned within 15-20 minutes (as the common / base solutions are already installed). This was the first website for that environment, however, when it was more than 24 hours, we then raised a Microsoft Support Ticket for it.
Microsoft acknowledged this as a bug and also got the fix ready, but there was a delay in deploying it because of dependencies internally.
In parallel, they also provided us with a workaround, which fixed the issue for us.
The steps are as follows –
Create Web Site with the Customer Self-Service Portal template.
Create Web Site with the Partner Portal template.
If Customer Self-Service Portal is not needed, the website can be deleted then, followed by deleting the below Managed solutions specific to Customer Self-Service.
Recently we had to change the password of the user account being used as an owner of the cloud flows as well as the used for connection/connection reference.
So we tried it on a trial environment first, below is our flow that runs every 5 minutes and creates a contact record (Dataverse), sends an email (Office 365 Outlook), and creates a file (SharePoint) owned by the same account along with the connection reference.
Below is our cloud flow
We can see the details around Connection References and Owner. We can also see it running successfully getting triggered after every 5 minutes.
Now let us update the password of the account that is being used in the flow.
Interestingly after password change our Flow kept running successfully without any errors.
Contact records are created in the Dataverse.
Mail sent using the Send an email action.
Files getting uploaded using the Create file action of SharePoint.
Also, we see the status of the connections showing as Connected.
It could be because Power Automate might be using cached credentials for a certain period after the password change, and/or the connections that use the refresh tokens to maintain authentication, have their tokens still valid.
Here what we can do immediately after changing the password is open the connections and click on Switch Account, sign in again using that account. That will referesh the connection.
That is exactly what we did for our Prod and other environments after we updated the password and we didn’t face connection failed issues or any other error for all our exiting flows.
Below is an example where we didn’t refresh the connection and got the below reconnect / failure message after the password was changed.
Focused view in Dynamics 365 that allows users to view and manage all their records in one place, allowing them to be more productive, as they can stay on track and avoid getting sidetracked by switching between multiple screens to find the information they need.
We can enable and disable it for all the records from the Power Platform Admin Center
Let us select the Focused View for the Cases.
Focused View lists all the records of the view, from where we can select the record, and see its details, within the same screen.
We can search, filter, sort, select multiple records, and further customize it.
Search –
Filter –
Select multiple records and perform bulk operations –
From Settings, we can customize the appearance of it –
Here we can specify maximum 4 rows and each row can have a maximum of 3 columns added to it, it can be from the same record or the related record.
Here we have updated it as follows
Next, we have admin mode, where we can lock the customization so that users won’t be able to change it.
From the Default View settings, we can specify the tables on which we want focused view as default.
Below we can see the Focused View updated to show Case Title, Case type, Created by, and associated customer’s email address.
Nishant Rana's Weblog 