Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic SYNERGY (steve huntington)
Decrease font size
Increase font size
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
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 17-Nov-2006 14:15
User is offline View Users Profile Print this message


Coman Wakefield

Posts: 18
Joined: 1-Jun-2005

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

Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 15:34.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.