This requirement typically arises when organizations generate tax letters, receipts, or periodic statements using Apsona and need clearer, more descriptive PDF names, both for future merges and for large numbers of older files already attached to Person Accounts or visible in customer portals.
A complete solution involves two steps:
(1) setting up dynamic naming for newly generated files, and
(2) bulk updating the names of historical files already stored in Salesforce.
A. Dynamic Naming for Future Merges
Apsona supports custom file naming from within merge actions.
How to set it up:
Open the Merge Action settings (Step 2).
Choose Field to use as file name.
Select the calculated field or any merge field producing the final filename.
All future PDFs generated by the merge will automatically adopt the custom naming format (e.g., Tax Letter 2024 – John Smith).
B. Mass Renaming Existing Files in Salesforce
Apsona can bulk update stored file names so legacy files match the new structure.
Process Overview:
Classic → Attachment
Lightning → ContentVersion / ContentDocument
Create a report or filter on the file object.
Export fields such as:
Record ID
Current File Name (Title / Name)
Parent record (Account / Person Account)
Use Import/Update mode
Operation: Update existing records
Map:
File ID → Salesforce Record ID
New file name → Title (ContentVersion) or Name (Attachment)
Running the update renames all files instantly without needing to download or re-upload them.
Key Takeaway
Future merges → Controlled via dynamic naming fields in the merge action
Existing files → Renamed in bulk using Apsona’s export + update workflow
This ensures consistent naming conventions across historic and newly generated records—especially important when exposing documents in customer portals.