You are here:
Errors (Managed Package)
For the managed package runtime, review error messages provided by the Omnistudio Build Tool.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
- Not Found (Managed Package)
For the managed package runtime, generally errors are due to missing or incorrect references to other objects. - No Match Found (Managed Package)
For the managed package runtime, errors that occur during export often cause errors during deployment. Errors during deployment also occur when a Salesforce Id reference isn't found in the target system. - SASS Compilation Error (Managed Package)
For the managed package runtime, when SASS fails to compile, the issue is generally related to the export not including VlocityUITemplates that are referenced as part of the SASS compilation. - Validation Errors (Managed Package)
For the managed package runtime, deployments run all of the triggers associated with objects during their import. Because there are various rules across the data model, sometimes errors occur due to attempts to create incorrect data. These issues must be fixed on a case-by-case basis. - No Configuration Found (Managed Package)
For the managed package runtime, here are some suggestions if you see the No Configuration Found error. - Duplicate Value Found (Managed Package)
For the managed package runtime, some errors are related to conflicting data. - Multiple Imported Records Incorrectly Create the Same Salesforce Record (Managed Package)
For the managed package runtime, these errors mean there are duplicates in the data. - Some Records Were Not Processed (Managed Package)
For the managed package runtime, this error means that during the deployment, some of the records that exist as part of the data pack data were not upserted into Salesforce.
Not Found (Managed Package)
For the managed package runtime, generally errors are due to missing or incorrect references to other objects.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Error >> DataRaptor --- GetProducts --- Not Found
The Omnistudio Data Mapper Not Found error means that likely someone deleted or changed the name of the Data Mapper being referenced without updating the Omniscript that uses it.
Error >> VlocityUITemplate --- ShowProducts --- Not FoundThe VlocityUITemplate --- ShowProducts --- Not Found error during export means that something, likely an Omniscript, has a reference to a VlocityUITemplate that isn't currently active or doesn't exist in the org as a VlocityUITemplate. In some cases the VlocityUITemplate for an Omniscript can actually be included inside the Visualforce page in which the Omniscript is displayed. In that case, the error can be ignored.
No Match Found (Managed Package)
For the managed package runtime, errors that occur during export often cause errors during deployment. Errors during deployment also occur when a Salesforce Id reference isn't found in the target system.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Deploy Error >> Product2/02d3feaf-a390-2f57-a08c-2bfc3f9b7333 --- iPhone --- No match
found for vlocity_cmt__ProductChildItem__c.vlocity_cmt__ChildProductId__c -
vlocity_cmt__GlobalKey__c=db65c1c5-ada4-7952-6aa5-8a6b2455ea02
In this error, the product being deployed is the iPhone with global key, 02d3feaf-a390-2f57-a08c-2bfc3f9b7333. The error states that one
of the product child items couldn’t find the referenced product with global key, db65c1c5-ada4-7952-6aa5-8a6b2455ea02. To address the error, the
other product must also be deployed.
No match found for indicates a reference field on the
SObject with missing data: <SObject>.<FieldName> or
in this example, vlocity_cmt__ProductChildItem__c.vlocity_cmt__ChildProductId__c.
Next, the error indicates what data is in the data pack's saved reference: vlocity_cmt__GlobalKey__c=db65c1c5-ada4-7952-6aa5-8a6b2455ea02.
This value is the global key of the Product2 being referenced by the field, ChildProductId__c on the SObject ProductChildItem__c. If it’s
clear that the referenced data exists, Product2 with vlocity_cmt__GlobalKey__c=db65c1c5-ada4-7952-6aa5-8a6b2455ea02, make sure that the
matching key for this SObject type is correctly aligned between your two environments.
SASS Compilation Error (Managed Package)
For the managed package runtime, when SASS fails to compile, the issue is generally related to the export not including VlocityUITemplates that are referenced as part of the SASS compilation.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
SASS Compilation Error VlocityUITemplate/cpq-total-card
Failed to compile SCSS:
.\VlocityUITemplate\cpq-total-card\cpq-total-card.scss SASS
compilation failed, see error message for details: Error:
on line 2 of /stdin
>> @import "cpq-theme-variables";Export the missing data with this command:
vlocity -job <JobFile> packExport -key VlocityUITemplate/cpq-theme-variablesValidation Errors (Managed Package)
For the managed package runtime, deployments run all of the triggers associated with objects during their import. Because there are various rules across the data model, sometimes errors occur due to attempts to create incorrect data. These issues must be fixed on a case-by-case basis.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Some errors are related to potential data quality issues. For example:
Product2/adac7afa-f741-80dd-9a69-f8a5aa61eb56 >> IPhone Charger - Error - Product
you’re trying to add is missing a Pricebook Entry in pricebook >>2018 Pricebook<<
Please add product to pricebook and try againThis error indicates that one of the child products that’s being added to this product might cause issues because the child product isn't in the 2018 Pricebook. The most simple workaround is to temporarily disable the listed pricebook. This error is generally caused by a cascading failure and can also be solved by deploying the listed pricebook on its own with a command like this example:
vlocity packDeploy -manifest '["Pricebook2/2018 Pricebook"]'
No Configuration Found (Managed Package)
For the managed package runtime, here are some suggestions if you see the No Configuration Found error.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
AttributeCategory/Something -- DataPack >>
Something -- Error Message -- No Configuration Found: Attribute Category MigrationRun packUpdateSettings or add autoUpdateSettings: true to your job file.
Duplicate Value Found (Managed Package)
For the managed package runtime, some errors are related to conflicting data.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
For Attribute Category Display Sequence you receive this error:
Error >> AttributeCategory/Product_Attributes --- Product Attributes ---
duplicate value found: <unknown> duplicates value on record with id: <unknown>
This error means that a unique field on the object is a duplicate of an existing unique field value. Unfortunately it doesn’t always provide the actual Id. Update the display sequence value for an existing attribute category object in the target org.
Records with the same display sequence can be found via this SOQL query:
Select Id, Name from %vlocity_namespace%__AttributeCategory__c where
%vlocity_namespace%__DisplaySequence__c = %DisplaySequence__c from
DataPack.json file%Multiple Imported Records Incorrectly Create the Same Salesforce Record (Managed Package)
For the managed package runtime, these errors mean there are duplicates in the data.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Catalog/Data – Datapack >> Data – Error Message – Incorrect Import Data. Multiple
Imported Records will incorrectly create the same Salesforce Record.
vlocity_cmt__CatalogProductRelationship__c: 20MB Plan
Multiple records exist with the same data for the product name,
vlocity_cmt__CatalogProductRelationship__c: 20MB PlanThe matching key for a CatalogProductRelationship__c
object is:
%vlocity_namespace%__CatalogId__c, %vlocity_namespace%__Product2Id__cThis error means that there are two references to the same product inside the same catalog, which isn't allowed. Remove the duplicates from the source org and re-export.
Some Records Were Not Processed (Managed Package)
For the managed package runtime, this error means that during the deployment, some of the records that exist as part of the data pack data were not upserted into Salesforce.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Product2/adac7afa-f741-80dd-9a69-f8a5aa61eb56 -- Datapack >> IPhone Charger -- Error
Message -- Some records were not processed. Please validate imported data types.
There’s likely a mismatch between the configuration data in the target org compared to the
source org. To solve this issue, rerun packUpdateSettings
in both orgs.
