[Zubersoft]

Geoff, your link is only slightly related to the topic at hand - this is about the FileSavePicker which doesn't provide a way for you to pick the initial folder that is shown. I'm not sure what you were wanting me to see from that link. Also, without unrestricted access to the file system, I can't create a folder anywhere on the system that I want, so I can't just default to a last known folder with a new name. The user has to pick this through Microsoft's file picker or I won't be granted access to create that file.

Jazzy - are you saying you want me to default the file name in the file picker to the last used file name? That is in complete contrast to what other users have asked for, as it would then overwrite the last file you created. The last thread on this is where I was asked to use the standard name generated by MobileSheets with the current day's date. I can't have it both ways.

Mike

[Swissmedia]

Jazzy - are you saying you want me to default the file name in the file picker to the last used file name? That is in complete contrast to what other users have asked for, as it would then overwrite the last file you created. The last thread on this is where I was asked to use the standard name generated by MobileSheets with the current day's date. I can't have it both ways.

Mike

It is the same.

If you save the last name, this become the default name + the date, like now.

The only problem is :
 In "MobileSheets_2025-02-13.msb" you forces "MobileSheets_.............msb

Now, imagine the file and directory is saved :

Drum_2025-02-13.msb
Singer_2025-02-13.msb
rhythm_2025-02-13.msb

What's the difference for you ?

Save the path, the name, tronk the date and incremant the date with the same procedure.

If user keek "MobileSheets_2025-02-13.msb" OK
If user change name, remember the new name.

I personally mistake saving "Drum" backup on the "Rhythm" backup...

It help, and nobody will see anny difference.

In ADDITION : Let me give you an idea, you plan to have a concept of "category" of songs (Drum-Rhythm-Singer, etc) because sheets avec same name but not same Key. This could be a Parameter for the future...

[Zubersoft]

That's making a lot of assumptions about the format the users enters for the name, and the format they use for the date (i.e. YYYY-MM-DD, YYYY_MM_DD, MM_DD_YYYY, etc). Am I supposed to try to preserve all that too? Because that's adding more and more complexity when I have higher value features that are being requested. I can add this to the backlog, but I will probably take a simple approach and be more rigid with the expected format, and if the user doesn't follow that, then I would fall back to the current behavior. Or I could add a setting to control the backup name formatting that supports a more complex syntax, but once again, that requires a lot more work, so I need to see many users saying they would utilize it for it to be worthwhile compared to other requests.

Mike

[Lester]

... that's adding more and more complexity when I have higher value features that are being requested.

If the cost of spending development time on faffing around with a filename which users can change to their liking is to lose Mike's pressing on with higher value features then I vote to give Mike free reign to decide which features will help most. After all, it's Mike's app and he should be allowed to decide which features are of higher value.

[Swissmedia]

... that's adding more and more complexity when I have higher value features that are being requested.

If the cost of spending development time on faffing around with a filename which users can change to their liking is to lose Mike's pressing on with higher value features then I vote to give Mike free reign to decide which features will help most. After all, it's Mike's app and he should be allowed to decide which features are of higher value.

At the moment the "group integration" do not exist.

1) no way to have 3 to 5 profiles" (All groups have minimum 2 profiles, in Jazz band probabily more)
2) Mobile sheet is not oriented for chorals and big formations, or assuming every parts of the group are responsible (Big SMILE)
3) In at the moment situation, backup are very complex for end users. The risk of mistake is permanent.

Rare are the formations using only numeric support, because, right now, sheets programs do not imitate end user preferences...

For us, if you remember the backup name, we ca have a backup for eatch section and a spare tablet rapidly restored in case, wit the good backup. Having profiles per type (Singer-UT Rhythmic-Blowers-battery-etc) would be better but whe don't ask for revolution...

Right now, befor each concert, it is a stress to be confident wit numerical sheets.

[itsme]

@SwissMedia: Maybe you should think about your workflow, how to work with the plenty of features MobileSheets already has.

1.) "Collections"
One collection for what you call a "profile". One database for all "profiles". Change collection to switch between profiles.
2.) separate libraries
A separate library (database) for what you call a "profile". Use "Library Settings - Switch Library" to switch between profiles.
3.) a combination of 1.) and 2.)

"Mobile sheet is not oriented for chorals and big formations, or assuming every parts of the group are responsible (Big SMILE)"
If you look around in the forum you can find examples for users of all kind of musical styles and group sizes that are more than happy with MobileSheets.
E.g. search for user "Oz Cello" in the forum. He organizes the sheet music for his string quartet on different tablets and has described his workflow clearly
https://www.zubersoft.com/mobilesheets/f...10421.html
https://www.zubersoft.com/mobilesheets/f...-9491.html
https://www.zubersoft.com/mobilesheets/f...-6413.html

@Mike: for scenarios with several libraries it would help a lot to use library name + date as backup name. Using ISO date yyyy-mm-dd as it is currently the case is perfectly fine.
MobileSheets_yyyy-mm-dd.msb as backup name for mobilesheets.db would stay unchanged.
Using uppercase/lowercase as it is in the library name would look nicer as using the all lowercase database filename .
In my example shown in this screenshot    
e.g. the backup name of MSPTest / msptest.db would default to MSPTest_2025-02-15.msb

[Swissmedia]

Everyone sees noon at their door (expression in French). I also managed to manage a workflow. 
But ask yourself why Mobile Sheet does not simplify all this? 

It takes a Geek to organize the workflow, and it takes another to connect MIDI...

And your moderation did not speak about having a spare solution in concert, another geek ?...

For the dates, you are right, the profile name + the reverse date is the right option to not add confusion.