Hi @nickva7 We are running into something similar.
Until the campaign object is released, we are using a workaround for campaign relationships. In other words, we want to tie projects to campaigns in a one to many ability.
- We create projects whose type is campaign and each campaign gets two calculated fields assigned:
- One that is the campaign custom ID used for internal reporting and UTM deployment
- Another that is a CONCAT of multiple fields, including the above ID, and more importantly is a user friendly/recognizable campaign name that users can pick from.
- We separately have a field called "related campaign" that is going to managed by our intake manager. Anytime a campaign project is created, the intake manager will copy the value of the CONCAT campaign name into this field.
- When a user creates a project that is a deliverable (a paid ad, for example), they'll be able to use a multi-select dropdown on "Related Campaign" thereby connecting all content and experience deliverables to that campaigns under which they are activated.
In an ideal world, after 1.b above, Workfront would automate and add the newly generated value to a running list that makes up the "Campaign Related" field and which could be used for reporting. Going to post this in the ideas section because it feels like a good workaround if they don't release campaigns.