Using line items in FaaS and sending to Salesforce

[KevinDillon]

Hi,

If I create a donation page with FaaS that includes multiple line items (as shown here: https://manual.clickandpledge.com/Fo...ct_Information) and a donor selects multiple items, how many donations get created in Salesforce for this transaction? Is it one total or one per line item selected? Also, I've been told that you can link a donation to existing product record in Salesforce via the item SKU matching the product Salesforce ID.

However, I believe the object being created here is actually an opportunity line item, which has lookups to opportunity and price book entry (I don't think there's a direct product lookup on opportunity line item). Is the appropriate Salesforce ID to match the SKU the ID of the price book entry?

Thanks,

Kevin

[CnP.Support]

Kevin,

It all depends on the C&P Settings:

Click to enlarge


If the Opportunity > Product is not enabled then for each item in the basket there will be an Opportunity created. Each Opportunity's name will be as set in ItemName1, ItemName2, ..
If the Opportunity > Product is selected then the Opportunity name will be the Transaction Order Number and each item in the basket (ItemName1, ItemName2, ...) will become products.

Assuming that the Opportunity > Product is enabled both at Salesforce Settings and C&P Settings > Opportunity then:

• If any line item (ItemName1, 2, ..) SKU matches the Product Code then the same product will be attached to the opportunity
• We only use the Standard Pricebook and not different price books.

Hope that answers your question. Please let us know if we can be of more assistance.

[KevinDillon]

Thanks for clarifying this. I do have a question regarding matching to existing products based off the Salesforce field ProductCode. Since this field is not unique, what happens if two products have the same ProductCode and a donation is submitted with a matching SKU? How does CnP determine which product to link to?

[CnP.Support]

Kevin,

We match against the first one since the query is set to LIMIT 1. We take the first instance of the match and assign it.

Hope that helps.