Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Filtering a datasheet on a field can change the displayed value for the parent
Filtering a datasheet on a field can change the displayed value for the parent
CMS-XML TeamTrack API: Changing Dependent Field Values
When attempting to set field values via a TSDisplayField object and your workflow has dependent field values , you can only select dependent field values for the independent field selection. If the independent field selection is changed, dependent field values for that selection are not re-loaded and calls to SetDisplayValue() on the dependent field TSDisplayField object return failure. To work around this problem, use two transitions and set the independent field value in one transition and the dependent field value in the second transition.
CMS-XML Single selection field values change status when mashup imported from file
Single selection field values change status when mashup imported from file
CMS-XML Form Action: The event "a field changes value" does not fire after the field is updated by a different form action
Form Action: The event "a field changes value " does not fire after the field is updated by a different form action
CMS-XML Dependency is not honored for multi-user fields when the independent (parent) field value changes
Dependency is not honored for multi-user fields when the independent (parent) field value changes
CMS-XML Binary fields using radio button style fail to have their values set/changed by form actions
Binary fields using radio button style fail to have their values set/ changed by form actions
CMS-XML Single Selection fields with default values cause change history record with no change via App Script.
Single Selection fields with default values cause change history record with no change via App Script.
CMS-XML Unix only - Since Upgrade to 6.6 transitions do not work if a multi-value field has a transition override which changes its value
Unix only - Since Upgrade to 6.6 transitions do not work if a multi- value field has a transition override which changes its value
CMS-XML $CHANGES() E-mail Template Tag Returns Incorrect Values for Backlog Priority Field
$ CHANGES () E-mail Template Tag Returns Incorrect Values for Backlog Priority Field
CMS-XML Tracking Report Changes and Deletion- no value for Field Specification if Use Advanced SQL Conditions - @where missing
Edit a report and change the Query type from User Basic Condition to User Advanced SQL Conditions. This was picked up in the Change History of reports but there is no value in the column “New Value” for Field Specification Changed Value. Similarly if you change it back again the prior value does not contain the "Prior Value" clause.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs