web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Quote Revision Bug in CRM 2016

(0) ShareShare
ReportReport
Posted on by 1,214

Hi All,

I'm facing a issue with CRM 2016 Quote Entity. All was working fine until recently. All a sudden system is not allowing me to Revise Quotes, I can do all the other things like Create, Delete Quote. Once the Quote status changes to Active from Draft, then I'm not able to revise it again, the error I get is..

"The entity cannot be updated because it is read-only"

Log File:

Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: The entity cannot be updated because it is read-only.Detail:
<OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts">
<ErrorCode>-2147220946</ErrorCode>
<ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" />
<Message>The entity cannot be updated because it is read-only.</Message>
<Timestamp>2016-11-23T12:24:32.8588768Z</Timestamp>
<InnerFault i:nil="true" />
<TraceText i:nil="true" />
</OrganizationServiceFault>

Need a solution to this urgently!

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Gary Letter Profile Picture
    1,267 on at

    If there are any scripts or plug-ins running on the Quote form, try disabling them and see if you still get the error. They might be trying to run an update action on the form after the form has been disabled.

    Check this thread for other possible solutions:

    https://community.dynamics.com/crm/f/117/t/118401

  • Karuna Karan Profile Picture
    1,214 on at

    There are no scripts, pluggins even the workflows that run over this entity has been disabled. Changing the state back to Draft using WF is not a ideal solution. As we do product demo to our customers, implement and use this internally.

    This is the 4th bug I found with this 2016 update. All of them are affecting the years old features.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
ScottDurow Profile Picture

ScottDurow 2

#2
GJones Profile Picture

GJones 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans