Use a response from another project

Cross-project Response Piping provides the ability for Blue to pipe response data gathered from a previous project (source project) into a new project (target project) to create highly targeted questions that are able to leverage previous responses. Learn more about possible use cases, the ins and outs of Cross-project Response Piping, and how to pipe responses from one project to another. For more information on default piping/field mapping symbols, see Default piping/field mapping symbols.

Why should I use Cross-project Response Piping?

Cross-project Response Piping is the perfect feature to use when responses from a previous questionnaire are needed to serve as a guide in a new questionnaire. This feature effectively allows you to conduct highly targeted queries focused on progress and improvement over any time frame. With Cross-project Response Piping a manager performing a 360 review of a direct report will be able to see how that employee performed during the last evaluation cycle, which may have an impact on the current evaluation.

What Should I know about Cross-project Response Piping?

Cross-project Response Piping is a powerful feature governed by a few rules to ensure both privacy and data integrity.

THINGS TO KNOW ABOUT CROSS-PROJECT RESPONSE PIPING

Responses will only be piped into a target project if both the subject ID and the rater ID match the subject ID and rater ID of the source project.
Cross-project Response Piping is not supported in preview mode at either the question or form level.
Only responses that have been submitted can be piped into a target project.
Responses cannot be piped from a confidential project.
Responses cannot be piped from a public project.
Responses cannot be piped from a survey project.
Responses to Date/Time questions cannot be piped.
If the scale marker is omitted, S1 will be used by default.
Responses from Personalized Comments, Personalized Single Selection and Personalized Single Selection Table questions cannot be piped.
Responses should only be piped into the Fill Out Labels.
If a questionnaire has been unsubmitted, it's responses will not be piped.
In the event that the user did not submit the questionnaire, the question identifier cannot be found, or the project ID is no longer valid then responses will not be piped and "(unavailable)" will appear on the questionnaire.

How is Cross-project Response Piping implemented?

The syntax for Cross-project Response Piping is:

[#P1$<QuestionIdentifier>|<Scale>,<Defaultvalue>]

#P1 - Indicates that this field mapping symbol is used for Cross-project Response Piping and not Response Piping.
QuestionIdentifier - Used to identify which question the responses should be piped from. Both questions and sub-questions can have identifiers. Identifiers must be unique.
Scale - (optional) The question scale for the response desired, possible values are:
- S1 for the first scale
- S2 for the second scale
- C for comments in a Single Selection or Single Selection Table question
Defaultvalue - (optional) The text that will be displayed if there is no available response found.

Examples include:

[#P1$A15|S2,your favorite color]

[#P1$Q10]

[#P1$DPT08,the location]

Where can I set up Cross-project Response Piping?

Cross-project Response Piping piping symbols should be added to the Fill Out Labels of questions in the target project questionnaire. Most question specific fields including: question title , details, help, scale caption, and option label fields will pipe responses, however text areas like the welcome message, thank you message and other project wide fields will not.