‘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

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 Azure Synapse Link / 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.

Posts on Azure Data Lake

Hope it helps..

Advertisements

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


When we create an environment in the Power Platform admin center, we get the option of specifying the datacenter region, but not the location within it.

Find the Data Center Region / Location of your Dataverse Environment- https://nishantrana.me/2021/04/27/finding-the-datacenter-region-location-of-the-microsoft-dataverse-environment/

E.g. we have specified Region as the United Arab Emirates.

Now within the UAE region, we had our environment created in the UAE Central location. However as per the data residency guide, UAE North should be the main location, and UAE Central is reserved for in-country disaster recovery.

https://azure.microsoft.com/en-in/global-infrastructure/data-residency/

Considering this we had our other Azure Resources / Subscriptions including Storage Accounts, created in UAE North.

However, while configuring the Export to Data Lake service, we got the below message in the Power Apps maker portal.

The storage account must be in the same region as your Dataverse Environment.

Your environment is located in UAE Central

Please attach a storage account in one of the following location(s): UAE Central

Considering our storage accounts were created in UAE North, we either had the option to create a storage account in UAE Central or to move the Dataverse Environment to UAE North from UAE Central.

Based on the recommendation from Microsoft Fast Track Architect and Azure Architects, we opted for the second option of moving the Dataverse Environment to UAE North from UAE Central.

For this, we raised a Microsoft Support Ticket from the admin portal and scheduled the movement for the non-prod environment first.

The movement took around 30 minutes (around 6 GB storage size), however, it was not reflecting in the Power Apps Maker Portal. The Microsoft team had to perform few steps manually in the background which took around 2 more days for the change to reflect in the portal.

Then we scheduled the same for Production (around 15 GB Storage Size), this time it took around the same 30 minutes and after the confirmation from the Microsoft team after 1 hour or so we were able to see the location updated in the Portal (there were no manual configuration steps needed this time) and were able to configure Export to Data Lake service with the storage account located in UAE North.

Posts on Azure Data Lake and Dynamics 365 – https://nishantrana.me/2020/12/10/posts-on-azure-data-lake/

Hope it helps..

Advertisements

Finding the Datacenter region / location of the Microsoft Dataverse environment


The other day we had to figure out the Datacenter region of our Dataverse environment. As we are aware within a particular geography there can be different Datacentre region at different location.

https://azure.microsoft.com/en-in/global-infrastructure/data-residency/

For e.g. within United States geography, we have following Datacenter region at corresponding Location.

Central US, East US, East US 2, East US 3, North Central US etc.

One of the ways is by checking the product availability by geography report.

https://dynamics.microsoft.com/en-cy/report/getgeoreport/

Check Dynamics 365 App and Power Platform features availability at different geography

GA

The other way is through Export to data lake service within Power Apps Maker portal.

Login to https://make.powerapps.com/ and

select Data > Export to data lake and click on New link to data lake


It will list down where the environment is located at as shown below.


Similarly, for an environment created in India having following locations

Pune, Chennai and Mumbai.

we can see the location of the environment  – South India

More on – Azure Architecture and Management –

https://nishantrana.me/2020/09/29/azure-architecture-and-management-introduction/

and Azure Data Lake https://nishantrana.me/2020/12/10/posts-on-azure-data-lake/

Hope it helps..

Advertisements