You might notice, after migrating your quote templates to another org with data loader (to production perhaps), you see either double or duplicate columns in the Quote Template!
Are you migrating the quote templates through data loader?
You must keep in mind that the order to add the Quote template through data loader is:
1. Quote Template
2. Template Content
3. Template Section
4. Line Column
5. Additional Documents can be added.
But it must be taken into account that salesforce has an automated process and that is that every time a Quote template is created, it creates 6 Line columns by default:
– QTY –> SBQQ__Quantity__c
– PART # –> SBQQ__ProductCode__c
– DESCRIPTION –> SBQQ__Description__c
– UNIT PRICE –> SBQQ__ListPrice__c
– DISC (%) –> SBQQ__Discount__c
– EXTENDED –> SBQQ__NetTotal__c
So, when we load the Quote template through data loader in the first step these 6 Line Columns are created automatically; Then when the creation of the quote template is finished, these 6 Column Lines should be removed if they are not being used.
7 thoughts on “When Migrating Quote Template Through Data Loader”
This is helpful.
Can you also please help me explain one of the questions that I had received in the exam.
What is the best way to control the increasing SKUs in the Org
Some of the options were
1) Use Preserve bundle setting in Package Settings –> Unlikely
2) Use Nested Bundles –> I guess it is not
3) Use Option Layouts
I would like to know if we have more detail on the question.
To control the creation of Product Options that can be understood as SKUs, we can use some validations.
1. In order to create the Product Options, the Configured SKU (Parent) and Optional SKU (Child) are always required, looking for no orphan product option and to avoid registrations without function.
2. On the other hand, in the package configuration, we have the option of “Allow Option Deletion” to allow product options used on prior quotes to be deleted; Then we can control when to delete or not these product options.
About these options that you tell me, one of the ones that by default can control the creation of skus is The “Preserve Bundle Structure” field ensures that bundles on amendment quotes have the same configuration as the quote that the sales rep amended.
Since it ensures that when you create an amendment or renewal the correct lines related to the correct Product Options are created.
**I hope this will help you, the question itself is a bit confusing and I do not know if we have another available answer option or any term that we need in the question.
One possible approach to reduce SKU proliferation is by using Configuration Attributes. But I don’t see as an option in the question. Example, I don’t need to create SKU for each color of the product.
I think the question is about how we can reduce SKU proliferation. Maybe use “charge type”/ equivalent etc to create different flavors of the same product rather than creating new products,
e.g. license fee product with charge type as “onetime” and “yearly” rather than creating two products. license fee onetime and license fee yearly.
Thanks for the commentary about SKU proliferation. But what does that have to do with migrating Quote Templates?
Thanks for sharing your knowledge. I have a question related to this. Thanks
What is the correct order of data import to load Products into CPQ?
3. Pricebook Entry
4. Product Feature
5. Product Option
6. Product Rule
6. Other Records related to Product (ie. Configuration Rule, Configuration Attributes, etc.)