We've fixed an issue where Salesforce Files generated through Apsona Document Merge were setting the FirstPublishLocationId field to the ID of the user running the merge instead of the source Salesforce record. With this update, FirstPublishLocationId is now correctly populated with the record from which the merge was initiated, making it easier for Salesforce Flows, integrations, and downstream automation to identify and process files associated with specific records. This improvement is particularly beneficial for customers using file-based workflows and integrations such as Box.