Referencing Fields on a Custom Form to Pre-populate a Field on another Custom Form?

[ChaseTaggart]

We created a custom intake form to intake top-level campaign information that is used to populate our marketing calendar with planned work.  This form just capture basic info about the campaign to help with visibility (via the calendar) and resource planning (for in-house team to see when campaigns are being planned to launch throughout the year).  This form contains a field for "Primary Line of Business".

The second step in the process is to populate the strategy brief form - much longer, much more detail about the campaign that marketers fill out when it's time to actually start kicking off the campaign.  In this form we have a field for "Audience".  We have very different audience choices based on the "Primary Line of Business" (the field already populated in the first intake form).  

How can I create a dependency for only certain audience choices to show in the strategy brief based on the selection from the intake form?  These are all custom fields, so native ref doesn't apply.

Probably super simple, but I don't know what I don't know!

[Sven-atClient]

Hi @ChaseTaggart 

Typically you'd want to do this with display logic, ie, if a Primary Line of Business has a certain value, show a specific Audience field. If there are multipel dependent field, use a section and apply the display logic to the section. 

If you have to have 2 forms, it seems to work when you put the Primary Line of Business on form #2. It will have the same value as Primary Line of Business  in the first form. And in the second form you can then apply display logic. 

Unless there's a good reason, I would stick with one form and sections. 

[Sri_Nijs]

Hi There!

You will use the same 'Primary - LOB' field on the second form and may be have to add Multiple Audiences fields with different options and apply corresponding Display logic with 'Primary-LOB' options. So that user will see Audience field with proper options which he/she is looking for but in reality in the back end you have Audience A, Audience B, Audience C and so on..