1 Reply Latest reply on Jan 5, 2019 4:35 AM by Julian Wigman

    Attempt to write to attribute "_[old ticket numbers attribute]" of a read-only IncidentManagement.Incident lifecycle object. When a lifecycle object reaches a read-only status they cannot be modified except through a lifecycle action.

    JohnO Specialist

      Hi Everyone,

       

      I've been trying to import tickets including their ticket numbers so our technicians would be able to locate the old ticket numbers. I get this error from the log.

       

      Attempt to write to attribute "_[old ticket numbers attribute]" of a read-only IncidentManagement.Incident lifecycle object. When a lifecycle object reaches a read-only status they cannot be modified except through a lifecycle action.

       

      Any help is always appreciated!

      Sincerely,

      John

        • 1. Re: Attempt to write to attribute "_[old ticket numbers attribute]" of a read-only IncidentManagement.Incident lifecycle object. When a lifecycle object reaches a read-only status they cannot be modified except through a lifecycle action.
          Julian Wigman ITSMMVPGroup

          JohnO I presume in your import setup you have selected a process and you have mapped the status field.

           

          As with some other recent posts you have logged you are finding that Service Desk does not allow you to update data when you are at a status that is defined as read-only.  These are typically ones of “end status” type but they also don't have to be as you can choose behaviour when creating your own statuses.

           

          I think i’ve come across this before myself in the past and what I did to workaround for a one-off import was to temporarily add a new status branch to my process (lets say called “Closed(Import)”) and then change the status values in my Excel import data Status column to this instead of “Closed”.  In my process i linked the inbound side of that to some temp action (use a manual “move on” for example) off of the Resolved Status and most importantly have a precondition after my new status testing if i am at that status and linking to a ”move on” automatic action finally linked up to the normal “Closed” status.

           

          Hopefully you get what I mean.

           

          So the import encounters a row in the import spreadsheet for a closed Incident and creates it and jumps to the “Closed(Import)” status, the precondition then automatically moves the Incident to the closed status for you.  Thus in essence you are importing to a non read-only status for closed Incidents with the process engine doing the final status move for you.  Once the import is run you can then remove the temporary status branch you had grafted onas you dont need that anymore.

           

          Julian

          MarXtar Ltd

          1 of 1 people found this helpful