Views:

Applies to Product - Microsoft Dataverse

What’s happening?
Users are encountering errors when attempting to create tasks from existing case records, receiving a "Transaction Not Started" error. Additionally, some users face a generic SQL error when trying to save or update contact records.


Reason:

  1. For the task creation issue, it appears to be related to missing privileges for the users attempting to create tasks. Specifically, users may lack the necessary "Action" privileges on the relevant entities.
  2. For the contact record issue, the error is attributed to inactive process actions associated with the appointment activities, which need to be activated for the operations to succeed.
Resolution:
  1. For the "Transaction Not Started" error when creating tasks:
  2. Verify the user's security role and ensure that the necessary "Action" privileges are granted. Specifically, check for the "prv{NAMEPII}Action{NAMEPII}" privilege on the "Action{NAMEPII}" table and add it if missing.
  3. For the SQL error when saving contact records:
  4. Activate the necessary process actions that are currently inactive. This can be done by navigating to the customization settings in the CRM, locating the relevant actions, and ensuring they are published.
  5. If the issue persists, ensure that no processes are running in the context of inactive users, as this can also lead to error messages.