locked
BPF issue during CRM 2011 TO CRM 2016 Upgrade RRS feed

  • Question

  • We are doing an upgrade project from CRM 2011 to CRM 2016 and we are facing an issue with the BPF on case for existing records. The already existing case records after upgrade have processed, stageid and traversedpath as null.

    Now when the records are opened by the user the default processid, stageid and initial traversedpath are set for that particular record.
    Now, when a user having only Read Privilege opens an existing case record, we are getting an permission denied error because CRM is trying to set processid, stageid for that record although user does not have write privilege on that record. Has anyone come across this issue?

    Also we are seeing an unusual behavior, for a user with read only privilege although the form is readonly, in JavaScript code we are getting formtype as Update and not ReadOnly. Has anyone seen this behavior in CRM 2016?
    Wednesday, April 20, 2016 5:30 PM

All replies

  • Hi Siddesh,

        Can you provide details on how you performed your upgrade? That may shed some light on what is happening.

    John

    Wednesday, April 20, 2016 7:39 PM
  • Hi,

    We performed Migrate Upgrade from 2011 to 2013 and 2013 to 2015 using DB. Then in place upgrade from 2015 to 2016.

    We haven't installed any rollups in 2016.

    Thanks

    Thursday, April 21, 2016 5:04 AM
  • Hi Siddhesh,

    It is the OOB functionality that after upgrade the existing record will have the processed, stageid set and the traversepath as per the business process flow.

    Whenever we open an existing record, it tries to set the Processid and the Stageid for that record and as the user does not have the write privilege for that entity, as a result it gives an error permission denied error while opening an existing record.

    Thanks,

    Sam


    Dynamics CRM MVP | Inogic | http://inogic.blogspot.com| news at inogic dot com

    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Thursday, April 21, 2016 8:30 AM
  • Thanks Sam!!

    Thus in order to avoid the permission denied error, Is it advisable to set default processed, stageid and traversedpath using a SQL script for existing records?

    We have only 1 BPF for the entity, with stages corresponding to only that entity.

    Also we have custom built Quick case feature where a case record is created and closed in the background. We are getting similar issue when the user tries to open a resolved case where processid and stageid was not set. Is it advisable to set processed and staged for these records in the pre create plugin?

    Thursday, April 21, 2016 9:58 AM