A file attached in RDM, that is then downloaded, will be named the full path or original location

A file attached in RDM, that is then downloaded, will be named the full path or original location

avatar

Hi there,

  1. Create folder
  2. Right-click folder -> Add attachment
  3. Select a file to upload
  4. Right-click on the file in RDM -> Save as
  5. Save it in another location than before
  6. Filename of the file is now the full path of the previous location


Expected that it would only be the file name, not including the path.

Example of file saved in step 5 viewed in Finder.

d44a2f78-3f6f-41ba-b265-26f82d315829.png

All Comments (3)

avatar

Hello,

Thank you for reporting this issue.

I tried to recreate the behavior on my side by following the same steps you outlined, but I wasn’t able to reproduce the problem— he downloaded attachment kept only the original filename and did not include the full path.

Could you please confirm that you are using the latest version of Remote Desktop Manager for macOS? If possible, also let me know the exact version number you are currently running.
Once we confirm this, we can continue investigating further if needed.

Thank you for your collaboration.

Best regards,

Carl Marien

avatar

Hi Carl,

I have just installed latest version 2025.3.8.5 and could still reproduce the issue. Using Azure SQL server as source. macOS 26.2 on MacBook Pro M3.
Included screenshots of the steps I did:

Create folder
Name the folder and click Create
Right-click on folder -> Add -> Add attachment
Select the file to upload
Save the attachment to folder

Choose filename (pre-filled with full path) and location
File shown in Finder

00dff69b-3c03-4a8c-b333-0b3977c0999e.png

5709823b-58e5-44d9-9473-42cf749ac05e.png

29712eb0-aefd-4e51-94a7-199c6bcc9310.png

a19e3718-5c27-41ce-ae1e-5d5620d1758b.png

42f83937-fcc9-4c3e-983d-41e75d3cd0c3.png

7458ade5-1b77-411b-a6ce-d1df7792dab2.png

424958e1-2141-4ca6-a85d-b48ad8073675.png

avatar

Hello,

Thank you for the detailed steps and screenshots that were very helpful. I was able to reproduce the issue today on my end by following them, even though I’m fairly certain I performed the same steps yesterday without encountering the problem. ¯\_(ツ)_/¯

I’ve created an internal bug report for this issue so our development team can investigate why the full original path is being used as the filename when saving the attachment on macOS.

Thank you again for taking the time to document everything so clearly. If the team needs any additional details, I’ll reach out.

Best regards,

Carl Marien