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 KM-Dim7: Error - 2371 - Error format PB text is not allowed for Item Text...
In Process Modeller, you have defined specific formats which can be associated to this item type. If you are selecting an item type other than what is defined you will receive this error.
CMS-XML KM-Dim7: 2371- Error: format "format name" is not allowed for the item type "prod:project name"
DIM: 2371- Error: format " format name" is not allowed for the item type "prod:project name"
CMS-XML Dim CM 2009 R2.02: Eclipse / share project: COR0005191E error - Format ECL-12901600920 is not allowed for Item type EGL:PROJECT
=== The issue here is that changing the library filename generation has the side-effect of causing the CI command to generate a format of ECL-12345678. From the error, it seems that the user has formats assigned to item types, and as the newly-generated value is not known a-priori the error is generated.
CMS-XML Value display format no longer allows greater than nine fields
Value display format no longer allows greater than nine fields
CMS-XML Composer, mapping field, "mapped to" value allow format "fieldName" causing confusion, mapping disappear.
. Such mapping will not be saved anyway. If you click the fieldname when the fieldname display, then you will get the correct "fieldName(FieldDatabaseName)" format.
CMS-XML RM 11.2.3 - RM does not allow setting PUID that starts with leading zeros
A change request is open to address the questionable functionality> DEF200366 Changes format of PUID attribute wasn't saved correctly
CMS-XML ‘Compare to Baseline/Promotion...’ does not allow for SRD files
If a user attempts to compare a staging library component to a –x version for a library type that is held in stacked reverse delta (SRD/SD) format , the request will fail. The contents of the delta file will be used for comparison and not the fully reconstituted component.
CMS-XML KM-Dim9: Is there a way to save the configuration information that enter the format, types, design parts for an upload, so that when similar command is used, the information does not have to be re-entered every time an upload is performed via Data Migration Utility?
For Dimensions 7, 8 and 9 As an alternative to the DMU, upload can be used, which allows you to define all your upload options include the upload rules on the commandline before submitting the command itself so it runs non-interactively. You would store the upload rules in the pcmsfile which would be re-used for further uploads, therefore not requiring any manual input or cutting and pasting.
CMS-XML Problem: VM6.5: When placing an expiration date on a User in the Access Control Database, an error msg "Expiration dates prior to the current date are not allowed." occurs.
This happens when entering an expiration date in the create user database box or modifying the user. If the control panel/regional settings are set to MM/DD/YYYY and a date has been entered in the format of MM/DD/YY, the above error message will occur. If the date is entered in the correct format, no error will occur.
CMS-XML When SBM link is clicked in Outlook Express, app report is not format properly
When SBM link is clicked in Outlook Express, app report is not format properly
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs