knowledgecenter-breadcrum

Knowledge Center

21 May, 2022

[SOLVED] System. Exception: You cannot start a transaction with a different isolation level than is already set on the current transaction.

Posted on 21 May, 2022 by Admin, Posted in Dataverse Dynamics 365

[SOLVED] System. Exception: You cannot start a transaction with a different isolation level than is already set on the current transaction. Blogs

[SOLVED] System.Exception: You cannot start a transaction with a different isolation level than is already set on the current transaction.

Introduction

I faced an error while publishing customisation of an entity using plugin which is “System.Exception: You cannot start a transaction with a different isolation level than is already set on the current transaction“. I tried to search about it, and I found that most people encountered this issue while creating custom entity and custom attribute in it.

Solution

As you can see the error details says that we cannot start a two transaction with different isolation level at time. So, I decided to change plugin execution mode from synchronous to asynchronous so we can avoid starting two transaction at a time.

I hope this will help some of you.

Thank you.

Comment

This is a Required Field

Loading

Recent Updates

Email Storage Made Easy: Dynamics 365 Space Saving Tips
Blogs
29 Feb, 2024

Email Storage Made Easy: Dynamics 365 Storage Saving Tips

Email Storage Made Easy: Dynamics 365 Storage Saving Tips Introduction Microsoft's latest feature allows you to migrate email descriptions from CRM…

READ MORE
Blogs
28 Feb, 2024

How to enable the enhanced email template editor in Dynamics 365?

How to enable the enhanced email template editor in Dynamics 365? To activate the Enhanced Email Template editor for your…

READ MORE
RCA for ARC Migration Issue
Blogs
28 Feb, 2024

Troubleshooting Convert Rules Import Issue: Entity 'workflow' with ID Does Not Exist error in D365

Troubleshooting Convert Rules Import Issue: Entity 'workflow' with ID Does Not Exist error in D365 Problem Statement We implemented D365 Customer…

READ MORE