Xporter -Table Grid Integration should support Grid Custom fields.

Description

Xporter Cloud Integration with Table Grid currently supports standard Table Grid fields only. However, it does not support Grid Custom Fields, which were introduced as a newer enhancement to Table Grid functionality. Customers using Grid Custom Fields are unable to include, export, or leverage data from these fields through Xporter Cloud integrations.
Support for Grid Custom Fields should be added to ensure feature parity with standard Table Grid fields and enable customers to fully utilize Table Grid capabilities within their document generation and export processes.

User friction
Users who have adopted Grid Custom Fields cannot access or export this data through Xporter Cloud. This creates inconsistent behavior within Table Grid and limits adoption of newer Table Grid functionality.
Steps to reproduce (right now) / Actual Result:

• Create or configure a Table Grid with Grid Custom Fields - ref: https://tablegrid.atlassian.net/wiki/x/EgBiNg 
• Configure Xporter Cloud Integration.
• Attempt to reference or export data from the Grid Custom Fields.
• Generate the export/output.

Actual Result:
Grid Custom Field data is not recognized, accessible, or exported by Xporter Cloud Integration.
IMPACT
Customers cannot include important business data stored in Grid Custom Fields in their generated documents, reports, or exports. This reduces the value of both Table Grid enhancements and Xporter Cloud Integration.
 

What would improve if solved:{}

• Full support for all Table Grid data structures within Xporter Cloud.
• Consistent user experience between standard grid fields and Grid Custom Fields.
• Increased adoption of Grid Custom Fields without sacrificing reporting and export capabilities.
• Reduced need for manual data duplication and workarounds.
  Impact on stakeholders:
• End Users: Unable to export required data from Grid Custom Fields.
• Administrators: Must maintain alternative field structures or manual processes.
• Customers/Organizations: Reduced efficiency and increased risk of incomplete documentation and reporting.
• Product Teams: Feature gap between Table Grid capabilities and Xporter integration.
   

Current workaround:{}
Store data in standard Table Grid fields instead of Grid Custom Fields, or manually recreate/export the missing data outside of Xporter.
 

CONTEXT & EXAMPLES:
Grid Custom Fields are a relatively recent enhancement to Table Grid. Customers adopting these fields expect the same integration capabilities available for standard grid fields, including document generation and exporting through Xporter Cloud.

Concrete example:
A customer uses a Table Grid to track project deliverables and leverages Grid Custom Fields for calculated values, status indicators, or specialized metadata. When generating a report through Xporter Cloud, only the standard grid data is available, while the Grid Custom Field values are omitted from the output.
Workaround risk:

• Manual processes increase the likelihood of human error.
• Data duplication can lead to inconsistencies and maintenance overhead.
• Customers may avoid adopting Grid Custom Fields despite their benefits.
• Generated documents and reports may be incomplete or inaccurate.