[itsme]

I'm experimenting just recently with using SongIDs to share setlists. Every member of my band runs his own MobileSheets database, has his own song files and uses his individual naming conventions for the songs. Tired of having everyone editing his own setlists again and again I thought about a better solution. It seems a good idea to specify a SongID for every song in our repertoire. Every band member has to edit the SongIDs once in his individual database and from then on one of us can create a setlist and write it into a .mss file via "Share - Export song list". The others import that .mss file to create a setlist with the same name containing the same songs. As far as I investigated that, it seems to work fine.

Anybody out there who has experience with a similar workflow?

@Mike: what are your concerns against such a usage in detail? you mentioned several things in the other thread? We dont synchronize databases and we don't connect tablets by now.

We could use it "as is", but there's room for improvements:

Displaying the SongIDs and sorting by SongID is required to make sure that all band members have specified the same SongID for the same song.

It would be useful if MobileSheets made sure that SongIDs are unique per database. Currently it is possible to assign the same SongID to several songs which leads to undefined behaviour when a .mss file is imported.

Filtering by SongID could be improved:
Currently the SongID field can be selected in the search bar, but to find a specific SongID it has to be entered completely. Searching for SongID = 0 helps to identify songs without SongID, but there's no possibility to search for songs with any SongID or search for a range of SongIDs.

Readability of .mss files (as well as many other config files of MobileSheets) could be improved:
Currently .mss files don't contain any line breaks so they are impossible to read. My favorite text editor Notepad++ has an XML plugin with a "Pretty Print" feature that integrates line breaks and indentations into XML files. If I apply that to a .mss file it becomes nicely readable and still works fine. Such a kind of formatting could already be part of Mobile Sheets
   

If a .mss file with a setlist name that already exists in the database is imported (and the respective warning of MobileSheets is ignored) two setlists with the same name exist. It is not visible which one is which. It would be better if MobileSheets added a postfix like _1, _2 ... to make the setlist name unique or provide an option to modify the name during import.