Odd error modifying an OOB field

2015-10-16 Thread William Rentfrow
ARS/ITSM 9x on Linux/Oracle

A co-worker and I were working on his computer using Dev Studio 9.  We opened 
up the form RKM:KnowledgeArticleManager.  We were going to add a new status to 
the Field ID 7 field "Status".

So we added a form overlay, view overlay, and field overlay and saved it.  We 
also had to temporarily add the field to the view.

When we go in to add a  new status value we have to add three pieces of 
information - Status Value, Alias, Ordinal #.  He added that as I watched and 
hit the "OK" button.

At that point we get an error saying some of the alias values are not unique.  
However - they are.

We close it without saving and start over - this time we open the field 
properties to add to the field and try to hit "OK before doing anything (so 
it's just 100% OOB values in the field) and we get the same message.

Anyone run into this?  We're going to open a support case with BMC, but 
something is messed up with that.

William Rentfrow
wrentf...@stratacominc.com
Office: 715-204-3061 or 701-232-5697x25
Cell: 715-498-5056


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"


Re: Odd error modifying an OOB field

2015-10-16 Thread Lucero, Michelle
Hi, William:

Have you compared the values:


-  In Base Mode vs. Best Practice Mode

-  At the database level, comparing overlay schemaid's version of the 
enumerated value vs. the base schemaIds related enumerated value?
Michelle

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of William Rentfrow
Sent: Friday, October 16, 2015 12:33 PM
To: arslist@ARSLIST.ORG
Subject: Odd error modifying an OOB field

**
ARS/ITSM 9x on Linux/Oracle

A co-worker and I were working on his computer using Dev Studio 9.  We opened 
up the form RKM:KnowledgeArticleManager.  We were going to add a new status to 
the Field ID 7 field "Status".

So we added a form overlay, view overlay, and field overlay and saved it.  We 
also had to temporarily add the field to the view.

When we go in to add a  new status value we have to add three pieces of 
information - Status Value, Alias, Ordinal #.  He added that as I watched and 
hit the "OK" button.

At that point we get an error saying some of the alias values are not unique.  
However - they are.

We close it without saving and start over - this time we open the field 
properties to add to the field and try to hit "OK before doing anything (so 
it's just 100% OOB values in the field) and we get the same message.

Anyone run into this?  We're going to open a support case with BMC, but 
something is messed up with that.

William Rentfrow
wrentf...@stratacominc.com<mailto:wrentf...@stratacominc.com>
Office: 715-204-3061 or 701-232-5697x25
Cell: 715-498-5056

_ARSlist: "Where the Answers Are" and have been for 20 years_

--
This message, and any attachments, is for the intended recipient(s) only, may 
contain information that is privileged, confidential and/or proprietary and 
subject to important terms and conditions available at 
http://www.bankofamerica.com/emaildisclaimer.   If you are not the intended 
recipient, please delete this message.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"