Status Reason filter (Timeline control), Multiline field (Quick View Form) and Improved accessibility for BPF on mobile app – 2021 Release Wave 1


  • 2021 Release Wave 1 for Dynamics 365 adds a new Status Reason filter for the Timeline control.

Activity status reason filter will show the status reasons of all the activities in the timeline. For the total 5 activities in the timeline, the filter shows the corresponding status reasons of all the activities divided among Free, Draft, Pending Send, Not Started status.

  • Another enhancement is in the way the multi-line text field is rendered within the Quick View Form. Now users do not have to click and scroll on the field to see the full content.

Below is the Quick View Form of Contact within the Account entity.

  • Business Process Flow experience has been updated for the mobile app, making it similar to the web application.

Earlier – 

bpf1

Now – It includes the name and duration for the Business Process Flow within the Mobile App as shown below.

bpf2

Check other blog posts on 2021 Release Wave 1 :

Blog posts on 2021 Release Wave 1 – Dynamics 365

Hope it helps..

Advertisements

Fixed – Taskbar overlapping / showing in Full Screen in Windows 10


Occasionally we will face the issue where the Taskbar is overlapping the maximized screen / full screen.

The trick that has always worked for us is to open the Task Manager (right click the tool bar and select Task manager)

Right click and Restart the Windows Explorer.

Hope it helps..

‘Callback Registration Expander’ System Jobs stuck at ‘Waiting For Resources’


Something to be aware of while copying a Dataverse Environment …

Rajeev Pentyala - Microsoft power platform blog

We set up a new Dynamics Instance by copying from another Instance using ‘Copy environment’ option from Power Platform Admin Center.

We opted ‘Copy over’ as ‘Customization and schema only’, as we don’t need the data to be copied over to the Target instance.

On the Target instance we’ve started the Data Migration activity and noticed frequent connection timeouts. When checked the ‘System Jobs’, there were many “Callback Registration Expander” Jobs stuck at “Waiting For Resources” state.

Reason:

  • To understand “Callback Registration Expander” jobs , lets first understand Callbackregistration entity.
  • ‘Callback Registration’ entity stores the configuration of Processes and Cloud flows (i.e., Power automate flows).
  • So, if you create a new Flow on the instance, a new entry goes in to ‘Callback Registration’ entity.

  • Coming back to our issue, when we configured the new Instance using Copy option, “Callback Registration Expander” jobs from the source instance copied to…

View original post 88 more words

Dynamics 365 – The record could not be deleted because of an association


SharePoint & CRM

The record could not be deleted because of an association

The record cannot be deleted because it is associated with another record. If you contact support, please provide the tecnical details.

This is normally a horrible error message to come across and one I’ve been dealing with thanks to the Sample Data feature of CRM bugging out on me and leaving me with the job of removing everything myself.

Luckily the tools are there to sort this out in a logical manner.

View original post 175 more words

Single-Component Tabs in Model Driven Forms


Dianamics PCF Lady

Can you believe the featured image is a form? A model-driven form with a PCF on it, and nothing else?

Lately I’ve saw in the docs an excelent article on best practices for model-driven forms: “Design forms for efficiency“. Right to the end, there is a part about letting a control expand to the whole space available. This possibility seems to be in the sdk since a few months already, but I didn’t knew about it yet. So I’ve tried it out.

How it behaves?

The sdk tab.setContentType accepts two modes:

  • cardSections: That’s the default for a model-driven form
  • singleComponent: Maximizes the content of the first component in the tab.

So, if needed, we could use it on every tab. It will show only the first control, and all the others will be hidden.

Actually you can get pretty close to a “singleComponent” form, by customizing…

View original post 454 more words

DSF Error: CRM Organization cannot be found while configuring Export to Data Lake service in Power Platform


Recently while trying to configure the Export to Data Lake service from the Power Apps maker portal, we got the below error.

DSF Error: CRM Organization <Instance ID> cannot be found.

More on configuring Export to Data Lake service –

https://nishantrana.me/2020/12/10/posts-on-azure-data-lake/

The user through which we were configuring had all the appropriate rights.

https://docs.microsoft.com/en-us/powerapps/maker/data-platform/export-to-data-lake#prerequisites

  • The user had System Administrator Security Role in the CRM Organization/ Dataverse Environment.
  • The user also had the Owner Role on the Storage Account.

Eventually, we raised a Microsoft Support Ticket.

We had recently moved our sandbox CRM Environment from UAE Central to UAE North.

Migrate Dataverse environment to a different location within the same Datacentre region – Power Platform

However, as a part of the migration, few steps were still pointing to the old region, which was causing that error. The Microsoft Support / Operation Team quickly corrected it and we were able to configure the Export to Data Lake service without any further issues.

We didn’t face this issue in our Production environment, which was also moved to UAE North.

Hope it helps..

Advertisements