We've encountered the same challenge in our RENXT environment and strongly support this enhancement.

While Solicit Code Start Dates and End Dates can be maintained on constituent records, the End Date is not readily available in standard Query or export outputs. As a result, it is difficult to determine whether a solicit code is currently active or has expired when performing reporting, segmentation, data analysis, or communication compliance reviews.

Our team uses end dates to manage temporary communication restrictions, and without access to this field in exports, we must rely on manual review or develop workarounds outside of RENXT. Having the ability to export Solicit Code Start and End Dates would significantly improve data governance, reporting accuracy, and operational efficiency.

Please consider making these fields available in Query and Export so organizations can accurately identify active versus expired solicit codes and leverage this information in downstream reporting and integrations.

Also, if Solicit codes are added via consents and Business rules add the dates to the solicit codes and make it possible to export these dates

This is very important as we now have a text opt in and a text opt out solicit codes. Our text company requires us to add a text opt in date which we are gathering in RE, but we must guess that date given because we can't pull it into a list or report. Would love to see the ability to export the data.