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 Auxiliary table listing report not displaying Multi-User field values for search filter
Auxiliary table listing report not displaying Multi-User field values for search filter
CMS-XML Display value for Contact field values not consistent for cached and not cached Contacts table
Display value for Contact field values not consistent for cached and not cached Contacts table
CMS-XML Some fields are displayed as asterisk for field values at top of UI form headers.
Some fields are displayed as asterisk for field values at top of UI form headers.
CMS-XML TT661: Reported Defect DEF115535: Multi-select Field Values Display are Bunched Together in Notifications
TT661: Reported Defect DEF115535: Multi-select Field Values Display are Bunched Together in Notifications
CMS-XML CMN960 report displaying blank field values after 99,999 components listed.
Customer ran the CMN960 (Component Level Security Report) report on every component (no masking) and ended up with a report having 114,500 (includes header lines) valid components listed and 483500 (includes header lines) mostly blank lines that only had an ‘N’ in the ‘Entity Check’ field . The ‘Component Name’, ‘Component Type’ and ‘Entity Name’ fields were all blank. The overall number of components should be just over 500,000.
CMS-XML Multi-Select fields displayed as CheckBoxes values are incorrectly TOP aligned
Multi-Select fields displayed as CheckBoxes values are incorrectly TOP aligned
CMS-XML VDF should not display values of hidden fields in State Forms.
Value Display Format displays values of hidden fields in State Form. The transition forms behave correctly by displaying the values in asterisks. The State form should also display the values as asterisks when it is in the hidden section.
CMS-XML When using German locale numeric fields display incorrect values in change history reports
When using German locale numeric fields display incorrect values in change history reports
CMS-XML Auxiliary table listing report not displaying selection field values for search filter
Auxiliary table listing report not displaying selection field values for search filter
CMS-XML Editable Grid cannot save with -0.xxxx Floating Point Numeric Values - field values display as invalid and the 0 must be re-inserted manually for each field thus affected.
Editable Grid cannot save with -0.xxxx Floating Point Numeric Values - field values display as invalid and the 0 must be re-inserted manually for each field thus affected.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs