Form - Cross Linked setup - Revision history

Philip Lacey at 11:12, 16 October 2017

2017-10-16T11:12:20Z

Philip Lacey at 23:14, 9 November 2014

2014-11-09T23:14:44Z

Philip Lacey at 21:38, 10 June 2014

2014-06-10T21:38:07Z

Philip Lacey: Created page with "Cross Linked fields provide a very powerful way of allowing other campaigns provide the contents for a parent campaign. This type is available to all Form types. There are t..."

2014-06-10T21:37:21Z

Created page with "Cross Linked fields provide a very powerful way of allowing other campaigns provide the contents for a parent campaign. This type is available to all Form types. There are t..."

New page

Cross Linked fields provide a very powerful way of allowing other campaigns provide the contents for a parent campaign. This type is available to all Form types.

There are two Cross Linked form question types.

* Cross Linked Listing
* Cross Linked Search

The set-up is common to both, but the use is different in each case.

== Function ==

A cross linked type, will allow the contents of second form to be displayed / used in a parent form.

The listing type will provide a drop down list of all the records in the second form.

The search type will allow a lookup to be performed on second form.

== Worked Scenario ==

We have a form for events. In this form, we have a field where we want to keep which customer this event is for. The challenge is that the customer list changes often. We want to be able to give this to some other team to keep up to date.

So we build two forms.

A. Form [1] = Customer form. We add in name and any other fields we like. Most importantly we make sure the field mapping is set correctly and we carefully choose what our search fields will display. We add a few records into this form for testing purposes.

B. Form [2] = Event form. We build the event form as normal.

C. So we come to the point that we want in the Event form to store which customer the event is for. We could add a drop down list or similar but these are not dynamic and are not easily managed by another team. Instead we add a question into the event form of type "Basic - Campaign Listing" from the "Basic - Cross Campaign Type" section. We call the question "Customer".

D. We need to tweak the Cross Linked field. So we "Answer Values - Modify". In the text and value for the question we add "intCDA_1_Id" without the double inverted commas. The 1 is the Id of the Customer form.

Now when we go into the form, the drop down list will contain all the test records we added in step A. The data displayed in the drop down list will be the search fields selected to display.

E. If however there are too many customer to display in a drop down list, you can change the type to "Basic - Campaign Search". This then provides a pop up lookup screen for locating the record desired rather than creating a very large drop down list.

If you would like to know any more about this functionality or how to customise it, please get in touch with your account manager or use the Help Me! button at the bottom of your BE screen.

[[Category:Module Specific:Form Management‏‎]]
[[Category:Scenarios:CrossLinked Campaigns‏‎]]

@@ Line 1: / Line 1: @@
-Cross Linked fields provide a very powerful way of allowing other campaigns provide the contents for a parent campaign.  This type is available to all Form types.
+= Overview =
 There are two Cross Linked form question types.
-* Cross Linked Listing
+* Basic - Form Listing
-* Cross Linked Search
+* Basic - Form Search
 The set-up is common to both, but the use is different in each case.
 == Function ==
 A cross linked type, will allow the contents of second form to be displayed / used in a parent form.
-The listing type will provide a drop down list of all the records in the second form.
+* The listing type will provide a drop down list of all the records in the second form.  If you have more than 100 options consider using the search instead.
 We have a form for events.  In this form, we have a field where we want to keep which customer this event is for.  The challenge is that the customer list changes often.  We want to be able to give this to some other team to keep up to date.
@@ Line 33: / Line 67: @@
-'''C.'''  So we come to the point that we want in the Event form to store which customer the event is for.  We could add a drop down list or similar but these are not dynamic and are not easily managed by another team.  Instead we add a question into the event form of type "Basic - Campaign Listing" from the "Basic - Cross Campaign Type" section.  We call the question "Customer".
+'''C.'''  So we come to the point that we want in the Event form to store which customer the event is for.  We could add a drop down list or similar but these are not dynamic and are not easily managed by another team.  Instead we add a question into the event form of type "Basic - Form Listing" from the "Basic - Cross Linked Type" section.  We call the question "Customer".
@@ Line 41: / Line 75: @@
-'''E.'''  If however there are too many customer to display in a drop down list, you can change the type to "Basic - Campaign Search".  This then provides a pop up lookup screen for locating the record desired rather than creating a very large drop down list.
+'''E.'''  If however there are too many customer to display in a drop down list, you can change the type to "Basic - Form Search".  This then provides a pop up lookup screen for locating the record desired rather than creating a very large drop down list.
-If you would like to know any more about this functionality or how to customise it, please get in touch with your account manager or use the Help Me! button at the bottom of your BE screen.
+There are also tools to help mass linking called Parent-Child linking tools [[Parent-Child_Form_Record_Linking]]

← Older revision		Revision as of 23:14, 9 November 2014
Line 48:		Line 48:


−	[[Category:Module Specific:Form ~~Management‏‎~~]]	+	[[Category:Module Specific:Data Profiling]]
−	[[Category:~~Scenarios~~:~~CrossLinked Campaigns‏‎~~]]	+	[[Category:Module Specific:Form Management]]
		+	[[Category:Topic:Reporting]]

@@ Line 18: / Line 18: @@
 The search type will allow a lookup to be performed on second form.
@@ Line 29: / Line 27: @@
 So we build two forms.
-A.  Form [1] = Customer form.  We add in name and any other fields we like.  Most importantly we make sure the field mapping is set correctly and we carefully choose what our search fields will display.  We add a few records into this form for testing purposes.
+'''A.'''  Form [1] = Customer form.  We add in name and any other fields we like.  Most importantly we make sure the field mapping is set correctly and we carefully choose what our search fields will display.  We add a few records into this form for testing purposes.
-B.  Form [2] = Event form.  We build the event form as normal.
+'''B.'''  Form [2] = Event form.  We build the event form as normal.
-C.  So we come to the point that we want in the Event form to store which customer the event is for.  We could add a drop down list or similar but these are not dynamic and are not easily managed by another team.  Instead we add a question into the event form of type "Basic - Campaign Listing" from the "Basic - Cross Campaign Type" section.  We call the question "Customer".
+'''C.'''  So we come to the point that we want in the Event form to store which customer the event is for.  We could add a drop down list or similar but these are not dynamic and are not easily managed by another team.  Instead we add a question into the event form of type "Basic - Campaign Listing" from the "Basic - Cross Campaign Type" section.  We call the question "Customer".
-D.  We need to tweak the Cross Linked field.  So we "Answer Values - Modify".  In the text and value for the question we add "intCDA_1_Id" without the double inverted commas.  The 1 is the Id of the Customer form.
+'''D.'''  We need to tweak the Cross Linked field.  So we "Answer Values - Modify".  In the text and value for the question we add "intCDA_1_Id" without the double inverted commas.  The 1 is the Id of the Customer form.
 Now when we go into the form, the drop down list will contain all the test records we added in step A.  The data displayed in the drop down list will be the search fields selected to display.
-E.  If however there are too many customer to display in a drop down list, you can change the type to "Basic - Campaign Search".  This then provides a pop up lookup screen for locating the record desired rather than creating a very large drop down list.
+'''E.'''  If however there are too many customer to display in a drop down list, you can change the type to "Basic - Campaign Search".  This then provides a pop up lookup screen for locating the record desired rather than creating a very large drop down list.