Enable Sub-Table and Partial Table Mapping in Response Projects

Per Khalees KV's suggestion, I'm submitting this request on behalf of our asset management client, Silvercrest.

Overview
Silvercrest, an asset management client, needs greater flexibility when mapping tables within Response Projects. Specifically, they require the ability to map only a subset of cells within a table or to split a single table into multiple tables, similar to how text can be split today. This capability is critical for fully mapping standardized DDQs that contain complex table structures.

Current Challenge

Many DDQs, including the standardized Dahab asset management DDQ, contain large tables with multiple logical sub-sections.
Today, Responsive does not support mapping:
- A subset of cells within a table, or
- Splitting a single table into multiple smaller tables during mapping.
When sub-tables cannot be mapped, clients are forced to work outside of Projects by manually referencing the Content Library and copying responses back into Word documents.
This breaks the intended efficiency of Projects, limits reuse through Project Templates, and creates friction for users.

Proposed Enhancement

Introduce enhanced table mapping capabilities within Response Projects that allow users to:
- Select and map a defined subset of cells within a table as a response, and or
- Split a single table into multiple logical tables during the mapping process, similar to existing text split functionality.
Ensure mapped sub-tables behave consistently with other mapped content in Projects and Project Templates.

Expected Impact

Enables full and accurate mapping of complex, table-driven DDQs within Responsive.
Eliminates the need for manual copy-and-paste workflows outside of Projects.
Restores the efficiency gains Silvercrest expects from using Project Templates and the Project module.
Improves adoption and satisfaction for clients who receive standardized questionnaires with complex table layouts.
Strengthens competitive positioning if comparable platforms already support sub-table mapping.

Resources

A prior support ticket, TKT-209648 (“Silvercrest – ‘Mark Table as Answer’ Creates Multiple Duplicate Response Fields When Mapping DDQ”), documents this issue with screenshots and was ultimately closed without a solution.
Video demonstrating the issue: https://drive.google.com/file/d/11P4fwaHg6DBAVoUcWKsnYjmgnZz7cldy/view?usp=sharing https://drive.google.com/file/d/11P4fwaHg6DBAVoUcWKsnYjmgnZz7cldy/view?usp=sharing
The standardized Dahab asset management DDQ has been attached for reference.
Dahab (2025 blank) - Q3 2025 - Small Cap Growth Opportunity.docx

Thank you to the Product Team for your time and consideration. Please reach out if any further clarification is needed.

@Khalees V and @dineshkumar for visibility.

Find more posts tagged with

Future consideration

Response Projects

Status: Future consideration

Comments

Khalees V

@Susan Berger Can you share how frequent the customer responds to this file?

Susan Berger

@Khalees V I heard back from Silvercrest and wanted to share additional context. They receive approximately 15–20 Dahab asset management questionnaires each year. If we could enable mapping these questionnaires within Responsive and support creating reusable Project Templates from those projects, it would significantly increase the value of the platform for them given the recurring nature of this work.

Thank you for considering this and for taking a look. 😊

Khalees V

Thanks Susan. This is helpful. I am also checking with the team if we can do tech feasibility to fix this. Team is held up with roadmap priorities and unable to take this up now. But i will follow-up on this. Keep you informed when we take this for feasibility check.

FYI: @Viswanathan S

Susan Berger

@Khalees V and @Viswanathan S Thank you for considering this. I’ve encountered this limitation across multiple client questionnaires, particularly where issuers present all questions within large, complex tables. Adding this mapping flexibility would benefit a broad set of customers and would be a meaningful improvement for handling these recurring, table-heavy DDQs.