Hello @Product Management Team ,
I’d like to raise an enhancement request regarding attachments stored in BLOB cubes and downloaded from a Data View.
Current behavior (pain point)
When a user downloads a PDF via the attachment icon, the generated filename is not the original uploaded file name. Instead, it is automatically set to the member of the first Entity placed “By Row” in the Data View layout.
In practice, this is confusing for end users when they download multiple documents from the same Data View:
- filenames look similar or misleading
- users often need to open each file to confirm what it is
- they then have to manually rename files one by one (or risk keeping the wrong naming), especially if they didn’t notice the active selection at download time
Also, the original filename is never preserved when loading a file into a BLOB cube, which makes the situation worse.
Proposed enhancement
Provide an option to define the downloaded filename, ideally by allowing a dynamic naming pattern based on the Data View context, such as:
- concatenation of the “By Row” entity members (e.g., Customer + Period + Document Type)
- a configurable filename template like:
Customer_Period_DocType.pdf - optionally, keep the original uploaded filename as part of the template (if stored/available)
This would make each downloaded document immediately identifiable without extra manual steps.
Why this matters (additional value for broadcasting)
This becomes even more important with Broadcasting. If attachment filenames could be dynamically generated based on the data context used in the Advanced broadcasting rule, users would instantly understand what the attachment contains and why they received it — improving adoption and reducing back-and-forth.
Expected benefits
- Better end-user experience and trust
- Faster processing (no manual renaming / validation loops)
- Clearer broadcasting outputs and improved communication
Happy to share concrete customer examples and naming patterns we see in the field if helpful.
Kind regards,
Kevin
