SKU Suffix and Opportunity Record Type Not Mapping

[jkwok]

I just got off today's office hour session and was told to post here about the issue that I'm having, as there wasn't a way to figure it out on the call.

The first issue is that SKU suffix isn't mapping into Salesforce. The SKU comes in - just not the suffix. The order ID is here: 39619-1712281213373601003. We need the suffix in order to assign the primary campaign source of the opportunity.

The second issue is that the opportunity record type is not mapping correctly in Salesforce for one of the conditions we have set up. I have 3 conditions (see screenshot). The first condition maps fine, and so does the third. The second condition, if the SKU starts with staff, does not map the record type correctly. Order ID is here: 39619-1712281209319181003

Let me know if you need any more information.

[CnP.Support.AM]

Good day @jkwok

Would you please grant us login access to your Salesforce account and share the OrgID so that we can review whats going on?

Looking forward to hearing back from you.

[jkwok]

OID is 00D1I000000n7LD and I have granted login access. Thank you!

[jkwok]

It occurred to me we may not have had post-install steps completed - I wonder if that could be causing anything to go awry? In any case, would it be possible to have post-installation steps completed as well?

[CnP.Support.AM]

Good day @jkwok

In order to complete the post-installation we need to have the Force.com domain set up:



We recommend that you set this up with your domain name as the basis to ensure your brand is consistent.

Please let us know once this is set up.

[CnP.Support.AM]

Good day @jkwok

FYI, it is nothing to do with post-installation. For the first order number order number: 39619-1712281213373601003 all seems to be working as expected. The reason it didn't assign the primary campaign source because there is no such condition set/defined with that SKU.

Please see:

C&P Data:


Primary Campaign Source Settings:


In order to assign the Primary Campaign Source, you will need to set the condition with that SKU.

Regarding the second order number, one of our developers reviewing the case and we will update you shortly.

[jkwok]

I've deployed our domain, ywamsf.my.salesforce.com.

We have the SKU suffix set up - see screenshot. My understanding is that it should have been appended to the SKU "dts".

[CnP.Support.AM]

Good day @jkwok

Please see:




Please confirm your organization's website so we can set this up and complete the post-installation. Note that you cannot easily modify your Force.com domain name after the registration process.

Regarding the SKU, as you see in above C&P Data there is NO such SKU passed and as such, there is no way to map it.

Looking forward to hearing back from you.

[jkwok]

Ah, got it. I have set up the site was ywamsf.force.com. Sorry, I was confusing sites with my domain!

I'm still confused. Could you explain how SKU suffixes work on custom questions then? And how I can map to Salesforce fields using the SKU suffix? I was told that the SKU suffix should just append to the SKU "dts". When I selected that custom question answer for order number 39619-1712281213373601003, only the SKU was coming in, not the suffix.

[CnP.Support.AM]

Good day @jkwok

We have completed the post-installation.

Regarding the SKU suffix, it is strange. We have tested this in our instances but unable to replicate the issue. Maybe there was NO SKU Suffix set for that custom question at the time of that transaction processed.

Do you have any other latest order number which doesn't have sku suffix included though it was there in settings?

[CnP.Support.AM]

Good day @jkwok

We want to test it in your instance by reposting the data and we need your permission to do it.

Looking forward to hearing back from you.

[jkwok]

I am fairly sure that I've had the SKU suffix there the whole time, but yes, you can go ahead and test in my instance and repost the transaction. This Salesforce isn't live so there's no real data.

[jkwok]

I ran some more additional test transactions today and I noticed a few things happening.

For order # 39619-1712281209319181003, the SKU suffix actually went in correctly! I tested with the custom answer "DTS Cohort - Winter 2018". However, it seems like the wrong amount was charged. The payment form we have only allows for a $40 charge (GUID: 9675863b-0d26-4f47-bbab-bec245f59bba), but I got a $20 charge instead. I tried again and was charged the correct amount (Order ID 9675863b-0d26-4f47-bbab-bec245f59bba) - any idea what could be going awry there?

For order #39619-1801041657324871003, I tried a different custom answer "DTS Cohort - Winter 2019", and the SKU suffix was not mapping correctly still. So the SKU suffix mapping issue seems to be not working for that particular custom answer.

Additionally, any word on the issue with the opportunity record type not assigning correctly for Order # 39619-1712281209319181003?

[CnP.Support.AM]

Good day @jkwok

For the order# 39619-1712281209319181003 is processed from the following Form: YWAM Staff Fee Form (Form GUID: b651bc65-14af-40a2-8127-013f673de7e6) Campaign Name: YWAM - Staff. We don't see any custom question defined for this form and as such, there is NO SKU Suffix. The default amount for this form is NOW $15.

Regarding the charged amount, it seems that you have updated the form but not cleared the browser cache. Please note that whenever you update the form, please clear your browser cache and load the form to get all new updated information.

Would you please process a transaction from the following Form and let us know the order number so that we can review the issue with SKU Suffix? https://connect.clickandpledge.com/w...07213448536546

Note: Don't change any settings for the Campaign: YWAM - Discipleship Training School before processing the test transaction.

[jkwok]

Sorry, I meant Order #39619-1801041653457061003. This was processed on the form ID 9675863b-0d26-4f47-bbab-bec245f59bba, but was charged $20 instead of $40. Looks like a caching issue then.

I charged two orders to the form:

39619-1801051305429911003 - selecting DTS Cohort - Winter 2018 (January-June)
39619-1801051306059821003 - selecting DTS Cohort - Winter 2019 (January-June)

The SKU suffix went through fine on both, so it looks like whatever issue has been resolved? Both were charged $20, but likely a caching issue, so I'll make sure to clear it next time.

Has there been any word on the opportunity record type issue for Order # 39619-1712281209319181003?