[joshlemer]

I have a complex song title formatting like:

Code:

%COMPOSERS:${VALUE} - |%%TITLE%%SOURCE_TYPES: (${VALUE})|%

i.e. "Bach, Johan Sebastian - Aria (Violin 1)"

But when I export the files, the only option is to label the files as 

%TITLE%.pdf
i.e. "Aria.pdf"


Which loses the composer and part name and would be really confusing to have a folder full of such files.

It would be really helpful for especially backing up our entire library to pdfs.

[Swiss1000]

Let me advice you to create a song file name as complet as possible, before importing song in mobileshet...

[samibe]

I name all of my PDF files so that the filename can be used and no additional fields need to be added to the title 'composerlastname - songname - instrument.pdf' prior to importing. This prevents similarly named songs from replacing each other. Occasionally, I'll mistype something and I'll fix the title in mobilesheets.

[joshlemer]

I guess my workflow is that I don't manually manage the files at all.

About half of my songs are pdfs that are emailed or shared with me. On my tablet I "open" the pdf with MobileSheets, enter in all the fields in MobileSheets and completely ignore whatever the pdf happens to randomly be called. 

The other half of my songs are scanned through the MobileSheets scanning functionality. That just creates useless file names like 20250402_114952.pdf.

I think having to manually manage the same metadata in two parallel systems (both MobileSheets' Fields, and the underlying file names) is pretty tedious and prone to errors and inconsistencies and goes against the grain of how MS invites users to interact with their library (by all indication in the UI, users are encouraged to forget about file names entirely and let MS manage them).