Hi Caitlin, I've run into the same thing and think there may be a 3rd option. Rather than using the 'request campaign' option across workspaces, I'm looking at using a custom field and 'Change Data Value' to solve the problem. Example: Workspace 1 contains the campaign you would like to ultimately request from Workspace 2. For ease of explanation, lets call the campaign that lives in workspace 1 'send to sales'.
Create a custom field called 'reqCampaign'
Within workspace 2, rather than using 'Request Campaign' in the flow, use 'Change Data Value' and set the 'reqCampaign' field to 'workspace1.sendtosales'.
Create a Smart Campaign in Workspace 1 that listens for the reqCampaign field to get set to 'workspace1.sendtosales' and in the flow use Request Campaign on the 'send to sales' campaign. I haven't fully vetted this option but my team is just about to start testing this solution. It seems like it could allow for a fairly dynamic solution. **The workspaces would most likely need access to the same partitions to make the setup reliable. hope it makes sense!
Hi Edward, It seems to be pretty legit.
We tested the requestCampaign field for:
Definitely using this. Awesome solution.
Retrieving data ...