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-Dim9:2340-IOP_VARIANT_NOT_SPECIFIED Error: New variant is not specified
KM-Dim9:2340-IOP_ VARIANT _NOT_SPECIFIED Error: New variant is not specified
CMS-XML KM-Dim9: Reported Defect DEF80745: Adding new item via web client returns NULL as variant and object id
KM-Dim9: Reported Defect DEF80745: Adding new item via web client returns NULL as variant and object id
CMS-XML KM-Dim8: DEF73118: When using the RENAME command in dmcli, an error of "/NEW_ID cannot contain a variant, just an id" occurs
KM-Dim8: DEF73118: When using the RENAME command in dmcli, an error of "/ NEW _ID cannot contain a variant , just an id" occurs
CMS-XML 14.1.03 - AdminConsole - Design Part variant not being displayed.
After creating a new design part w/a variant "files" the variant does not display. Create a parent DP w/the variant value "files" Create a sub DP w/the variant value "files"
CMS-XML Dim9: Desktop Client: "Failed to find default to part variant" error
Exporting the Payroll process model and creating a new database sometimes resulted in an error message "Failed to find default to part variant ", on opening the design part view in the desktop client.
CMS-XML KM-Dim7: How to copy the design tree into new product from existing one
In the Process Modeller, in the create product screen remove the multiple entries for VARIANT from AAAA to just A. This change will copy the desing tree structure into new product, if the option for the copy design tree to new product is selected.
CMS-XML ModScript has functions that require the usage of Variant, let's offer other options
See Modscript documentation for the new options
CMS-XML Dim12: New imported based, create project reports table cannot be found
CREATE VIEW DEFAULT_OPTIONS ( PRODUCT_ID, VARIANT , PCS ) AS SELECT
CMS-XML Dim CM 12.2.2.2: CRDB /import incorrectly creates a top part variant of A for $GENERIC
Create a new base database using CRDB with the /import option to pick up the exported process model. This creates a new $GENERIC Product with the correct variant of AAAA in the new Base Database but the process then creates a top Design Part for the Product with the variant A which is wrong.
CMS-XML Dim10: VM2DM: PCM0005057E Error: Part variant :.AAAA does not exist
Within Admin Console, verify the Design Part variant under Product Administration/Design Part Structure. Once the new variant is noted, two options can be followed: Option 1:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs