After updating an ARO can no longer edit it

Eric_Krasner

When trying to edit an ARO after adding additional prompts, i get the following error message.  Has anyone seen this?

Message: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

Peter_Settle

Found this from @brett_moffett

Have you at any time edited the ARO with the standard editor? (Just double clicked rather than select edit Advance Request Offering)

This will corrupt the ARO. The only way to recover would be to recreate the ARO.

If you have run through the standard steps I would delete the ARO you have and recreate it making sure never to use the default RO editor in the Console and try again.

Peter_Settle

Totally agree with you. If it don't work remove the functionality so you don't mistakenly select it.

Peter_Settle

Have you attempted to Copy or Duplicate the ARO instead of editing it.

Eric_Krasner

I tried that and it didn't work.  I got the same error message when trying to "Edit Advanced Request Offering."  Funny thing is that I can edit it as a normal RO, just not as an ARO.

Peter_Settle

Found this from @brett_moffett

Have you at any time edited the ARO with the standard editor? (Just double clicked rather than select edit Advance Request Offering)

This will corrupt the ARO. The only way to recover would be to recreate the ARO.

If you have run through the standard steps I would delete the ARO you have and recreate it making sure never to use the default RO editor in the Console and try again.

Eric_Krasner

I figured that was where I was at.  Was just trying to avoid the inevitable. On a side note, it would be great if there was a way to remove the standard Edit RO from the double click action on the RO and replace it with the Edit ARO action.  Would solve alot of headaches.

Peter_Settle

Totally agree with you. If it don't work remove the functionality so you don't mistakenly select it.

Brett_Moffett

I agree @Eric_Krasner
We have tried many different ways to remove the default editor and\or remap the default double click method against request offerings but there is no supported way to do so.
Could we hack the whole thing? Maybe. But then it would invalidate the Microsoft support of the entire SCSM product.

Really sorry that this is the way it is and we certainly wish we could do more to make this easier for people.