When you do a complete database in Sentinel, does it also update your Favorites with any changes that occurred, IE: assigned TGID and Channel Name? Or do you have to recreate your Favorites? I was assuming it was but now I wonder.
No it does not make any changes to you favoritesWhen you do a complete database in Sentinel, does it also update your Favorites with any changes that occurred, IE: assigned TGID and Channel Name? Or do you have to recreate your Favorites? I was assuming it was but now I wonder.
No it does not make any changes to you favorites
Try and get Uniden to make any changes to this softwareWonderful!
I can understand why you might not want them to if you have special edited channel names, etc, but it should be an option to update or not to update them. Lower Michigan just had a bunch of changes. It would probably be easier at some point to recreate them then to try to keep up with editing them.
It is good that the database does not update favorites lists. It would insert all of the frequencies and talkgroups that you didn't want to monitor when you created the favorites list. Also, I edit the names of most alpha tags. I find that the ones in the database often are very confusing what they actually are.
It's not that simple. Mixing and matching which edits to keep and which edits to discard gets messy fast. The only viable solution would be to have a MS Word-style revision tracking and approval system, where the user is asked separately about each difference between the database and favorite list. For large favorite lists, that gets tedious really fast.I've long wanted the favorites lists updated with the database. I do understand that a lot of users don't for various reasons but a simple "Do you want to update your favorites lists with the latest entries for those systems" check box would work for both camps.
It is simple, if Uniden or RR were to assign a primary key to each object. You can then update specific objects efficiently.It's not that simple. Mixing and matching which edits to keep and which edits to discard gets messy fast. The only viable solution would be to have a MS Word-style revision tracking and approval system, where the user is asked separately about each difference between the database and favorite list. For large favorite lists, that gets tedious really fast.
They do; Uniden/Sentinel uses the unique object ID assigned by RR internally to connect systems, departments, sites, site frequencies, and channels. But that doesn't address the issue of conflict resolution when the database entry doesn't match the FL entry. There is no way to algorithmically choose whether to ignore a change/conflict between the database and a FL. You'd have to ask the user to choose how to handle every single individual conflict, whoich would spam the UI every time you updated the database. And even more people would complain about that.It is simple, if Uniden or RR were to assign a primary key to each object. You can then update specific objects efficiently.
A global option would make this quick work. Want the FLs updated automatically, then check the box. Another option available on each object would prevent an overwrite there. There’s no need to prompt the user at all.They do; Uniden/Sentinel uses the unique object ID assigned by RR internally to connect systems, departments, sites, site frequencies, and channels. But that doesn't address the issue of conflict resolution when the database entry doesn't match the FL entry. There is no way to algorithmically choose whether to ignore a change/conflict between the database and a FL. You'd have to ask the user to choose how to handle every single individual conflict, whoich would spam the UI every time you updated the database. And even more people would complain about that.
Updated how? If there is a difference between a FL and the database, there are 4 possible options:A global option would make this quick work. Want the FLs updated automatically, then check the box.
We have talked about this several times previously. Some folks want updated Favorites Lists, others do not. I'd say unless we were united in our wishes, Uniden won't be making any chances, notwithstanding Upman's passing.