Handle AutoNumber on reimport

Feature Request: Preserve AutoNumber as Separate Export Field

Summary:
Enable AutoNumber to export as its own dedicated column rather than being concatenated with other fields, and ensure it is handled correctly during reimport. This would prevent duplication and preserve the integrity of auto-numbered proposal data throughout the export and import workflow.

Problem Statement:
Currently, when a user exports the Auto Numbered proposal full RAM and then reimports it, the AutoNumber is duplicated. This happens because the AutoNumber is not treated as a separate field during export and import. The current behavior creates unnecessary cleanup work, increases the risk of data inconsistencies, and makes the workflow unreliable for users managing proposal data in bulk.

Proposed Solution:
Export AutoNumber as its own standalone column rather than concatenating it with other values.
Ensure the import process recognizes and maps the AutoNumber field correctly during reimport.
Prevent the system from duplicating the AutoNumber when records are reimported from exported files.
Maintain consistency between exported data structure and reimport behavior so users can safely round-trip proposal data without unintended changes.

Benefits:
Reduces manual cleanup caused by duplicate AutoNumbers.
Improves data accuracy and consistency during export and reimport workflows.
Makes bulk proposal data management more efficient and reliable for users.
Supports a cleaner, more predictable round-trip data process.

* * *