Overview
When the user uploads a source file into a project, the answer field is automatically displayed with the header “Response” instead of the expected “Answer.” The imported file also brings in additional information and dropdown values that are displayed as labels in the answer section.
Current Challenge
- After importing the source file, the answer section displays “Response” as the header, along with additional information such as “Exchange Funds/Structured Investments/…”, which the user does not want included in the answer field.
- The dropdown values from the source file are also being populated as labels, rather than only displaying the answer content.
- The user can currently resolve the issue by going into Answer Configuration and manually changing the response header to “Answer” and making the required field configuration changes.
- While this workaround resolves the issue, it is not practical for the user because their projects contain a large number of fields and questions. Repeating these changes manually for every project/import is time-consuming and increases the effort required to prepare the project.
Proposed Enhancement
Enhance the source-file import and answer configuration process so that the system can correctly identify and retain the intended answer header and field mapping from the imported file. Where applicable, users should be able to define their preferred answer header and mapping once and have it applied automatically during import.
The enhancement should also prevent unintended dropdown values or additional source-file information from being displayed as answer labels. This would reduce repetitive manual configuration and ensure that imported projects consistently display the answer section in the expected format.