![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: new custom CR attribute - having problems getting/setting CRData using API for CRs withouth the new attribute! Topic Summary: new custom CR attribute - having problems getting/setting CRData using API for CRs withouth the new attribute! Created On: 17-Nov-2006 14:15 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We've added a new custom attribute to a CR. None of our CRs yet have this attribute (obviously). the new attribute is intended for use with API programs that get or set CR Data.
I've got an API program that uses GetCRData and submitCR/ModifyCR to add/change CRs. I'm having problems referring to the new field in the list of attributes when I make these calls - the perl API seems to be complaining because the attribute isn't present on existing CRs. How can I handle situations where I'm getting/setting CRData and don't know if this attribute already exists in the CR or not? is there a specific way that this type of attribute should be defined? Thanks |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.