Cannot Deploy Multi Language Document Designer [Could not find component information]

(Doc ID 2149707.1)

Last updated on NOVEMBER 08, 2017

Applies to:

Oracle BigMachines CPQ Cloud Service - Version 2015 R2 to 2015 R2 Update 6 [Release 2015]
Information in this document applies to any platform.

Symptoms

Deploying and switching to a different language

Document in Document Designer cannot be deployed. Switching to a different language generates the same error. This is only observed with Multi Language templates.

Additional error from the bm.log shows this error, Caused by: Object 'varname = TEXT7966bf9f-5403-491a-b5b3-d9918c72f531, template_id = 6372525, code = 0' of type 'TeComponent' could not be found.

Note: When switching to a different language, not all languages generates the error. When a language generates the error, the document cannot be saved as well.

 

Copying the document

A second error can also show up when copying the document and setting it to the language where the first error shows up. The second error is An error occurred while trying to copy the template.

Additional errors from the bm.log are:

An error occurred while trying to copy the template
Unable to modify template key.
Caused by: Unable to modify template key.
Caused by: com.bm.xchange.db.DBException: Fatal database error: Could not perform update.
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (BM_{site_name}.SYS_C001366662) violated

 

Note: This issue is different from "Unable to Open a Document in Document Designer [Could not find component information] (Doc ID 2166228.1)" where the document cannot be opened at all.

Changes

When modifying the template, a translation is added to the text element and this translation is then deleted. Moreover, the second error is triggered when the deleted translation contains a conditional. The steps of the changes are as follows:

  1. Text element in English is added where English is the base language.
  2. A French translation is added to the text element.
  3. User switched to the French language to see the translation.
  4. A conditional is added to the text element. Template is saved. Note that at this point, the user is in the French language when the conditional is added.
  5. User navigates out of the template.
  6. User opens the template again in English, then does either of the following:
    1. Open the text element > switches to French> check use Default > click Ok. This process basically deletes the translation of the text element.
    2. Deletes the text element altogether > Save.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms