Start a new topic
Implemented

Scripts: support all database-fields

There are some database-fields, that are not supported by the script-engine:

- Grouping

- Catalog number

- Part of series*

- Popularity*

- Quality

- Lyrics

- Biography**

- Album version***


* This is part of NeonScriptAlbum, but it seems, it is not written into tags...

** This is part of NeonScriptArtist, but it seems, it is not written into tags...

*** This is part of NeonScriptAlbum and NeonScriptTrack, but it seems, it is always empty in NeonScriptTrack and thus not written to tags...


1 person likes this idea

These are all tag-fields and can be supported in the scripts.

Database only fields (favourite for example) cannot be supported directly in the script engine, it has to be handled via SQL.

"AlbumArtistSortOrder" is also missing.

By the way, is it a good idea to make IDs like "NeonScriptTrack.DetailId" writable?
Changing those IDs would completely mess up the database, wouldn't it?!

>>By the way, is it a good idea to make IDs like "NeonScriptTrack.DetailId" writable?

They should and could not be writable since they are handled by the database type itself.

For the actual script object, you can modify them but thy will never be written back to the database.

The requested fieldsĀ are implemented in our most recent release, 13.0.14923, released the 8th of January 2018.

Login or Signup to post a comment