Screen Shot 2015-11-02 at 10.50.06 AM.png

Custom Objects in Marketo - Part 6 - Many to Many Custom Objects

Level 6

Now lets move on to completing out many to many example. The example, as you may remember, is to model student enrollment in courses. Some terms I'll be using..

The "bridge" object Is the object that contains the data resolving the objects, the enrollment in this case. It tells us which lead is enrolled in which course, allowing many enrollments by many leases into many courses

The "edge" object is our standalone object. In this case, the course.

The example below may help. Here, the Opportunity Person Role is the "bridge" object and the Opportunity is the "edge".

Screen Shot 2015-11-02 at 10.50.06 AM.png

So lets continue by creating our enrollment object in marketo

Step 1: Create the Object

02.png

Step 2: Create Link Field #1 (to the Course Object)

03.png

Step 3: Link Field #2 (to the Lead Object)

04.png

Step 4: Create a Dedupe Field (EnrollmentID in this case)

Screen Shot 2016-01-14 at 11.22.13 AM.png

I really recommend thinking through what you want your objects dedupe fields to be. What makes the bridge object unique? In the case of the edge object its often just something like a course ID.. but for enrollment it might be EnrollmentID AND CourseID... or simply a GUID. Remember once you publish you cant change dedupe and link fields.. so think through it carefully!

Step 5: Publish The Object

05.png

This is how it looks...

06.png

That's all great.. but how do you use it? Great question. Under your triggers and filters you'll see the following

  • Added to Course (Trigger)
  • Was added to Course (Filter)
  • Has Course (Filter)
  • Was Not Added to Course (Filter)

The cool magical thing here is that when you select the filter... you can also see the bridge object! You can get a list of leads who have a Course with a certain instructor and also are enrolled in a program of study, for example.

Screen Shot 2015-11-02 at 11.37.03 AM.png

2441
18
18 Comments
Level 10 - Champion Alumni

I'm a little confused. In a lot of the docs, it seems that I must use a spreadsheet or API to populate these custom objects. Am I not allowed to connect these to other custom objects or to drop in the data via a form w/o using the API? Can I not use a flow action on them to create a new record for a custom object?

Hi Josh,

Unfortunately, I am afraid no, unless something new is coming up the way.

I entered this idea ​ a while ago specifically for this.

-Greg

John Mattos​​ I'm a little confused on Step 4, the text states 'create a deduce field' but the image shows publishing a field. I'm missing something?

Level 6

Yes! Apparently a draft got published.. check it out now.. its more complete, Edward Masson

Level 6

Josh Hill​ Hello! Unfortunately populating custom objects has to be done via the bulk upload or API (REST or SOAP). Grégoire MICHEL​ is correct in this.

Thank you sir. Looks fantastic and loving the series.

Anonymous
Not applicable

Apologies if I've missed this, but how can you use fields from the 'edge' object in, say, an email template?

Using the enrolment example above, could I pull details of each course that a student was enrolled into and send them an email with info about that course on enrolment?

Thanks.

Hello -

Did you ever come up with a solution to your question?  I have a similar question and was also wondering about if we had a date on the course custom object, if we could use that date as a date token in a flow step to send reminders.

Anonymous
Not applicable

I'm trying to follow the directions to do the same, but when I try to publish the 'Edge' object, I get the message 'Need Link For Publish'. Not sure what I've missed. Any ideas?

Hi Steve,

depending on what you want to achieve 2 solutions :

  1. The Bridge object should have 2 link fields. One towards the lead or account object, another one towards the edge object. Works for a lead <- course member -> model (The bridge in fact enables the n-n link)
  2. Or the Edge object should have a link towards the bridge one. Works for lead <- invoice <- invoice line item model

-Greg