#Product토론 중인 항목 6개

No, natively, ARM/Revenue Cloud doesn't let you search and add from "all products" the way Salesforce CPQ does..  

Natively, there's no way to search and add products in the Transaction Line Editor without going through Browse Catalog, and Browse Catalog is inherently catalog scoped; a product has to be catalog/category assigned to be searchable and addable there.  

For comparison: in Salesforce CPQ, clicking Add Product on the QLE pulls up a list of products based on your price book — there's no catalog concept in CPQ, so effectively every priced product is visible and pickable.

In ARM, Browse Catalog replaces that flow, and it's built around the catalog/category model by design — a product needs catalog assignment (plus price book entry, selling model, and indexing) to appear there.

By default, it is not possible to remove delete button from certain quote lines. It is somewhat surprising that Salesforce CPQ doensn't allow configuring a filter to hide specific buttons at the Quote Line level. 

The only target object that supports evaluating a Custom Action Condition for a Custom Action displayed in the QLE (Quote Line Editor) is Quote. The documentation states: "Custom actions can’t be conditionally shown or hidden on specific lines." 

I emphasize "only target object" because, when selecting Product as the target object, the documentation specifies: "Conditions can evaluate product fields only if your custom action appears in the configurator.”  

There are many use cases where preventing the deletion of a specific Quote Line would be extremely valuable.  

For instance, consider a Quote Line that represents transportation costs. This line (always one per Quote) is automatically added using a Product Rule, and its populated automatically through Price Rules. If you have a button that allows users to delete lines, it would be ideal to block deletion of this line, since every Quote containing products must include this cost. 

What other options do we have?

One alternative, although it result in a poor user experience, is to cerate a validation type Product Rule. The problem is that this doesn't prevent the Quote Line from being deleted. Instead, once the user deletes the line and attempts to save, a validation error appears. To save successfully, the user would have to manually re-add the deleted product. 

From there, I considered creating a Product Rule that automatically re-adds the missing product. However, after several tests, I was unable to make this work. Based on the documentation, it never going to work: "Quote-scoped product rules run only during product selection or bundle configuration. If the product rule’s error condition is based on quote or quote line data, Salesforce CPQ doesn’t evaluate the error condition until quote lines are added, which can require a second save during product bundle reconfiguration or product selection."

@Lukas Giese i am suspecting in that case that this product record could be corrupted.. and we may need a case to be raised with salesforce.. BUT to double confirm.. can you do below

1. Share screenshots of this product as well as product that you managed to edit and are in same pricebook. 

2. are there any lookup filter or lookup fields in the product record, wherein one of the lookup field records dont exist?

3. are you able to clone this product successfully?

@Aiswariya Devi, please instead, go to the product record you want to add, then click on the pricebook related list, click add standard price, and mention a price when askedhttps://help.salesforce.com/s/articleView?id=ind.insurance_add_a_price_book_entry_606216.htm&type=5

Eric

In case anyone else has had this issue -- I got confirmation from support that this a B2B bug, and it is currently being fixed. They'll release a fix in an upcoming patch.

What appears to be happening is that if you have products with variants, those product objects will not be available for indexing int he SEO settings in Experience Builder, and they will not show up in the sitemap.xml file. However, if you have products that do not have variants, those will work as expected. So it's only the products with variants that are having the problem.