HELP! We start class registration Monday 4 Jan.

[briegull]

Event: Winter 2021 - due to go live on Monday 4 Jan 2021

Box office works fine, as usual.

But when you register someone or some ones for a class, and then pay via “other” on the next screen, the “other” person (the payer) appears in the SF campaign as well as the person who was registered.

The payer does not show up as registered in the receipt,

They do not show up in C&P Registrations and don’t delete when we clear test regs.

They are not counted in the totals in C &P Basic Information

THEY ONLY SHOW UP IN THE SF CAMPAIGN course, and the Opportunities (which is proper). This throws us off because we produce class lists from that SF campaign, and check them constantly for other things.

This also happens if there are two people registered (for different classes) in a single transaction. When the payer is chosen (who is one of those registered for one class) they show up in all the classes as members in the SF campaign class.

This is, however, new since the last registration period in early November. Three of us have tried this, have watched each other do it on zoom. We have cleared caches repeatedly. We have deleted test registrations repeatedly. Somewhere in the past year there started to be a different handling of temp contacts, it looking like there were several entries to connect the t.c. to. We learned to select them all, and it worked fine. I notice that step no longer exists, but it looks like it is no longer working the way it did.

AMANDA BYRNE KNOWS OUR ORG WELL AND CAN HELP US - BUT WE NEED THIS ASAP!

PERMISSION GIVEN, ORG #00D36000000Hnko

THANKS!!!

[CnP.LiveSupport.AB]

Right now your Opportunities are being assigned based on SKU,

It does not matter that your Additional Information > Event tab is set to Winter 21, because the SKU rule will always overwrite the rule you have set on the Additional Information > Event tab.

When the registrant fills out the form, the instructions are to assign the Registrant and the Opportunity to the Winter 21 Campaign (from the Additional Information > Event tab), and the Attendee to the class' campaign (on the Additional Information > Levels tab). The Events app sends the transaction to the C&P account, it gets logged (which you can see in CONNECT), and then a copy of the transaction information is sent back to Salesforce and received by the PaaS app.

The PaaS app > C&P Settings has additional instructions to assign any transactions coming in with a SKU to be assigned to the class campaign - so rather than assigning the Registrant and Opportunity to the Winter 21 campaign, they are both assigned to the class campaign instead.

It's all about the order that the "instructions" are applied - the registration has the correct instructions, but because of the SKU, also has further instructions to be assigned once the registration is received by PaaS

Remove the rules you have for C&P Settings > Opportunity, and your Registrant and Opportunity should be assigned to the Winter 21 Campaign, and the Attendee will be on the Class Campaign.

Do you need to have the Opportunity on the Class Campaign, but still have the Registrant on the Winter '21 Campaign? That can be done but is a little illogical, because it separates the Campaign the Registrant is on and the Campaign the Opportunity is on- which can be confusing later if you're expecting to see the Opportunity on the same campaign as the Registrant.

~ Amanda

[briegull]

We need each sem to know the number of people registered in a given sem, regardless of how many courses they take.

I'm going to fix this now and try it out. THANK YOU SO MUCH FOR LOOKING AT THIS SO QUICKLY.

[briegull]

BUT WAIT - if we remove all the student sku assignments, what will assign the attendees to a given class?

[briegull]

I removed two of the skus pointing to the campaigns, for Autusm and National Security. Registered Joe Blow in Autism and Mary Row in security, and then paid by ME.
Joe DID NOT GO INTO AUTISM, AND I WENT INTO NATIONAL SECURITY AS WELL AS MARY ROW. THE RECEIPT IS CORRECT, ONE IN EACH, ME IN NONE.

I have used the sku to put people in the right class for years. Only difference is that this time we used the whole sku not just part of it. ?? The classes are children of Winter21. again used for years.

[CnP.LiveSupport.AB]

OK, the only remaining issue is that we need to make sure that you're assigned to the Winter 21 campaign.

So, you can either set a SKU rule like this:

SKU includes "w21stu", CampaignID is (the Winter'21) Campaign

OR

SKU includes "w21stu", "Use Transaction Campaign" (which is essentially instructing it to use the campaign assigned under Additional Information > Event Tab)

[CnP.LiveSupport.AB]

When C&P Apps refer to "Transaction Campaign" in Salesforce, they're referring to which SF Campaign the C&P Transaction record is assigned to. To help demonstrate this, I added a C&P Transaction Related list to your "COURSE Campaign Layout" and your "NPSP Campaign Layout" (NPSP Campaign Layout is used by Winter '21).

The mechanism for assigning the Registrant's Contact to a Campaign is based on which Campaign the Opportunity is assigned to where the Registrant is the Primary Contact.
The mechanism for assigning the Attendee's Contact to a Campaign is the Class Campaign (Event Management > Additional Information > Levels tab).

When the registration happens, the C&P transaction record is assigned to the Winter '21 Campaign.

If you set up a SKU rule:



then the Opportunity is assigned to the Winter '21 Campaign based solely on the SKU - the value set in Event Management >Additional Information > Event tab for Transaction Campaign is completely irrelevant.

If you set up a SKU rule:



When the Registration happens, the C&P Transaction record is assigned to the Winter '21 Campaign, and the Opportunity is assigned to Winter '21 because the SKU RULE is saying to use the same campaign that the C&P Transaction record is using, as set in Event Management >Additional Information > Event tab

I

[CnP.LiveSupport.AB]

I notice you still have all the other rules set up with "SKU includes" for the classes, without the "w21stu". Those are still going to add the Registrant and Opportunity to the Class Campaign :

In the past, the Attendee Contact was assigned to the Campaign based on the Opportunity, because the Opportunity does represent the "Line item"/"ticket".

But the Opportunity also represents "the income" - so now the Opportunity is always assigned based on a SKU rule- either to match to the "Transaction Campaign" or based on its SKU. This has probably been a change that has happened since you've used Events for class signup.

Trust me, the Attendee will get assigned to the Class Campaign as long as it is set under Event Management > Additional Information > Levels tab, you don't need these rules for that.