Recently while trying to register the plugin, we got the below error
Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). —> Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number).
It was because we were trying to register the assembly which was already registered in that environment, instead of updating it.
From the notes in the timeline, now we can link an existing note to an existing case, contact, or account record (this will unlink it from the current record) and also create either a new case, contact, or account record.
To configure it, open the Notes property of the Timeline section in the form.
Below we can see the different properties we can configure.
Enable the Link to Table Command
Enable the Tables to be connected.
Here we are enabling the Contact table, and then specfiying the Quick Create Form to be used while creating the new contact record, and also the mapping of the title and description field of the Notes. We have the same configuration for Case and Account.
Save and publish the changes.
We can now see the option to Link to record for the notes.
We get the option to search for an existing record (it will show results from tables connected).
Clicking on Advanced opens the lookup dialog.
On Associating to an existing record, the notes get linked to the new record and unlinked to the current record.
We can see the notes record associated with the contact record and removed from the existing case record.
We can also use the plus + sign to create new records of the tables connected from the notes.
Account, Case, and Contact in this case.
This opens the Quick Create form, with the title and description field of the notes mapped.
After the new record gets created, we are again presented with the option to Unlink that existing note from the current record.
Below we can see the new record with the note associated with it.
To delete the user from Power Platform, we need to enable the following feature – Delete disabled users.
Before enabling this feature we can see the following Views for the Users.
After enabling Delete disabled users, we can see 2 new views added,
Users not in Microsoft Entra ID but exist in the environment.
Users not in Microsoft Entra ID and soft deleted in the environment.
Also currently we can see 3 users (enabled) in the environment.
Now let us delete the test 1 user from the Microsoft 365 Admin Center.
The deleted user and its data can be restored up to 30 days (soft delete)
Inside Power Platform Admin Center, we can see the user account being disabled (and soft delete state in AD)
If we try to delete the record, we will get the below error that use is present in AD in the state SoftDeleted. Please permanently delete the user in Azure first.
Let us permanently delete the user in Azure AD.
Login to Azure Portal or Microsoft Entra admin center, select Users >> Deleted Users
Select the user (deleted) and click on Delete Permanently.
On Refreshing the user, we get the message that the user does not exist in the AD, and also user record is now moved to the “Users not in Microsoft Entra ID but exist in the environment” view.
Let us try deleting the user record from CRM now.
This time user records get deleted (soft delete) successfully.
Within the Power Platform Admin Center, we can see the user record moved to “Users not in Microsoft Entra ID and soft deleted in the environment”
Similar to Azure Active Directory or Microsoft Entra, now we get the option to permanently delete users from the Power Platform Admin Center after soft delete.
Here we’d have a quick look at the analytics capabilities of the extension.
To enable it, inside Visual Studio, navigate to Tools >> Options >> Kupp Code Analytics >> General or Extensions >> Kupp Code Analytics >> Analytics >> Configure Analytics
Set “Enable C# Code Analyzer” to “True”. Requires Visual Studio to be restarted on change.
To run the analytics, select Extensions >> Kupp Code Analytics >> Analytics >> Run
Below we can see the results of running the analytics on our sample plugin class.
Let us see the code analysis rules one be one.
PCA001: The lPlugin interface should not be used directly.
The suggestion is to use a custom base class instead to handle the call delegation, using the context information of the plugin.
PCA002: Plugins should be stateless. Remove all instances properties and values.
Plugins are instantiated on a per-request basis and handle specific execution contexts. The plugin instances are short-lived and should not be assumed to persist across multiple requests. Also if multiple plugin instances execute especially in the case of bulk operations, it could lead to concurrency issues.
PA002: Attribute collection should only include the changed attributes. Create a new entity for the update
While updating the table or entity, create a new Entity instance and only include those attributes that are changed.
PA001: Specify the required columns instead of retrieving all columns.
Specify the required attributes to be retrieved instead of all columns as this would impact the performance.
EBEA002: Late bound entities should be replaced with early bound entities.
It is suggested to use early bound entities as they provide Type Safety and IntelliSense Support decreasing the likelihood of runtime errors and can enhance productivity through auto-completing and context-aware suggestions.
These were a few of the examples, that show the key capabilities of the extension, for the complete list, please refer to the product documentation
We might get the below error while performing the update operation.
This could be if we have not specified the GUID of the record to be updated or if we are using an Alternate Key to update the record, we have not specified the KeyAttributes property.
We either need to specify the Id property or specify the KeyAttributes property
AADSTS700016: Application with identifier ‘6d8ff73a-27ef-443c-b524-d8b69ae87580’ was not found in the directory ‘w72tk’. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.
This could be if we have specified wrong Client or App Id.
Check the correct App Id either from Azure you can also refer to the correponding Application User created for it.
Nishant Rana's Weblog 