C&P Transaction object

[briegull]

Today I was working with Robert in the zoom support forum and he helped me find out why my C&P transaction information wasn't showing in a report that we were running based on a C&P report showing sweeps, etc for our accountant. It was because the TRANSACTION CAMPAIGN wasn't being filled, and this has to do with some changes made in the last year or so which we didn't discover because we don't use Connect most of the year (we use Event Mgmt for most payments for our senior college)
Now that I can look at the Object Manager to see various "hidden" objects, I looked at C&P Transactions. I am confused.
What we have is
a) in Connect a Campaign
b) in Salesforce a Campaig
c) in C&P Transactions there are THREE Campaigns, for different purposes, plus a Campaign sku field and an alias.

I would greatly appreciate it if someone could explain to me where all of these Campaigns draw their information. I assume that they are linked together with a sku as always.
And it would be fantastic if there could be a slight adjustment in the name of the field "campaigns" which is a lookup of SF, like "campaign-SF"

[CnP.Support.AM]

Good day @briegull

Campaigns in CONNECT are totally different from Campaigns in Salesforce. Previously, the CONNECT platform required you to have Salesforce Campaign statically assigned to each campaign, and then in SF you had to go and create the campaign and map them one to one.



With the new system in CONNECT, we are taking advantage of the success of ITEM SKU and give you the ability to create Campaign SKU which can easily map in Salesforce under C&P Settings > Campaign and simply point them to any campaign you want. If a change is needed you simply change the map and no need to go everywhere in CONNECT to make the changes.



How to Map? Campaign SKU mapping in Salesforce C&P Settings > Campaign: https://support.clickandpledge.com/s...tings-Campaign

Regarding the C&P Transaction Campaigns, on the C&P Transaction details page, you will see 3 Campaigns i.e.

• Transaction Campaign
• Opportunity Primary Campaign Source at the opportunity-related list
• CONNECT Campaign.

All of the Campaigns information is shown on the Transaction Details page:



The CONNECT Campaign Alias is a unique identifier for the CONNECT Campaign- you cannot use the same alias for multiple CONNECT campaigns and the same information will be listed on the Transaction Details page and Campaign SKU defined in the CONNECT Campaign will also be listed in Transaction Details page.

Regarding the Campaign naming, previously we do have only the Campaign Name field but later we added the Campaign ID which is why you see the same name. However, I have forwarded it to our developers to make the field label distinguishable.

Please let us know if we can be of more help.

[briegull]

Thanks! There is another name in C&P Transaction that is duplicated; it's Record Type. If you're trying to build a report in SF, it's hard when you don't know which one is which. Maybe the developers can fix that while they're at it.

For the purposes of record keeping, etc, sending emails etc, Campaigns in Salesforce are necessary. Without those campaigns we couldn't keep a record of who gave in the annual appeal in what years, etc. Connect is fine and necessary too but they do different things.

[CnP.Support.AM]

Good day @briegull

Would you please share the screenshot of where you see those duplicate Record Type names?

[briegull]

I am talking about the names of the fields in the object C&P Transaction. Not the contents of the field in the db. It certainly isn't "best practice" to have two fields with identical names in an object, even though by looking at them in the Object Manager you can see that they are very different. A lot of us old-timers actually do still build our own reports. And you can't see, in either Lightning or Classic, what the difference is between two fields with the same name. Just rename the display names of one of each, you don't have to rename the API or anything.

[CnP.Support.AM]

Good day @briegull

Yes, we are aware of that. Some of the fields are deprecated which will be changed in v10.

Sorry for the inconvenience.