Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Search results have actions showing on the left hand side as a list of text if you create a new database
To reproduce just create a new database in System Administrator and then change to point to it. Then go to Composer and create a New Process app.
CMS-XML Can't submit item with required Date field on a custom form and locale set to English (United States, Computer)
If you have a custom submit form with a required Date ( or Date/Time ) field and your Locale set in your User Profile is set to English (United States, Computer) you can't submit an item . ... Trying to submit a form in any of the custom shells like Work Center will result in the form not submitting and no visual indication that anything is wrong. ... Open the System Administrator tool
CMS-XML Back to Results button disappears after updating an item through a report
Development Manager 1. 0 Release Control 3.0Release Control Control 3.1Service Manager 2.0
CMS-XML Linking a subtask back to the parent results in error "item could not be found"
Having linked an item to a subtask, when you attempt to link the subtask back to the parent item , the error message " item could not be found" is displayed. This causes the system to hang and only an IIS reset fixes it.
CMS-XML Notification events for archived items give Application Log error: "Record xx, in Table xxx could not be found"
6) Open SBM System Administrator , and Archive items from this table (Tools > Archive ).
CMS-XML Large text field may result in scrolling issues in the Manage Auxillary Data section of Application Administrator
Observed problems include but may not be limited to: Truncation of rows and/or columns due to lack of vertical/horizontal scroll bars. Abnormal scroll bar size that may change suddenly when you attempt to scroll past the item with the large text field.
CMS-XML Change History Report doesn't display result if report is run against many items
If Change History Report is run against many items (example: 30,000 items , etc.), processing of the Change History Report takes long time, IIS process takes CPU time. Depending on how many items are processed in the report, Change History Report may not be able to display result.
CMS-XML DMCM: Fail to Get an item in a baseline when it's not in current project
Attempting to Get or Browae an item when it's not in current project results in the error: "Browse Item : 2320-Error: Item is not in Work Set
CMS-XML placeholder items on windows
a. An SDP trace reveals that the metadata creation routine RPC is sent to the build agent twice during target collection. This was probably the result of a failed attempt to fix metadata for placeholders. b. despite this, the resulting metadata is invalid.
CMS-XML Email from an item: After adding an attachment, the resulting link in the email is missing the server name, making the URL invalid (Paperclip Link)
This defect is NOT about attachments that are already on an item . Instead, this is about attachments that are added directly to an outgoing email. When the user receives the email, it contains a link to the attachment, but the link does not include the servername, making the URL invalid
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