invalid life cycle stage and stage status combination - field update error

[CJPeterson]

Hi All, 

Im working in my PDI trying to understand Life Cycle Stages and Status in the location table - cmn_location_list

When trying to update Life Cycle Stages field I get error message "invalid life cycle stage and stage status combination error message" but this is only in list view. I checked to make sure I had valid fields in the tables for Life Cycle Stages and Life Cycle Stages Status, but when trying to make an update in the location table I get an error. 

When updating in form view I am able to update. Does this happen because of ACL rules? 

[Ajay30]

Hello,

There seems to be two possibilities:

1. ACL rule written on Location table with Operation as "list_edit" and check in the logic in script section

2. Client script written on Location table with Type as "OnCellEdit" and check the logic in script section

Both of them you can see easily by just right clicking on the list header of Location and select Configure as below:

[Bharat Goyal]

Did you check the mapping as well ? 

[CMDB Whisperer · Accepted solution]

Actually this is a fundamental flaw/design issue that everyone will face if trying to edit lifecycle stage and status values separately from a list view.  If you use Hardware Status/Substatus (and of course you shouldn't, I'm just using it as an example) then you can set one field as Dependent on the other, which allows you to edit them both simultaneously from a single cell.  Since the Lifecycle Stage and Status fields are Reference fields, you cannot set one field as dependent on another, which means that if they are in a list view, then as soon as you select one and change the value, it will save the record immediately, but first it will attempt to validate the combination is acceptable, which it may not be.  The issue here is that what you really should be doing is editing both fields as a single action.  The only way to do this in a list view would be to set the editing so that it saves the record per row, rather than per cell.  This may not be feasible/desirable for you, depending on your list view, but currently that is the only way to avoid this.  To get around this problem ServiceNow would have to allow reference fields to be dependent on one another, and would need to introduce a new cell editor that allowed multiple references to be edited simultaneously.  That seems pretty unlikely to happen any time soon (and there is no longer a way for most user to submit this as an Idea to the Idea portal, because most people can no longer access it.)