Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Ferdi]

To manage my library I have created various custom fields. Some have to be manually filled (e.g., 'Rating on Pitchfork', 'Sync to Sonos'), others are calculated.

I have recently read some posts that address certain situation by creating expression columns. And now I am wondering what the cons and pros are!
For example, I have a calculated field 'Year - Album' (to list all albums of an artist in chronological order, with both release year and name of album in one field). Instead, I could create an expression column, but what value would that bring? Fields are re-usable.

Any thoughts on this topic at all?

[Hendrik]

Custom expression-based fields are automatically available everywhere. An Expression column is limited to the view you created it in. It greatly depends on what you are trying to solve here.
Show a certain computed value in one view only? Use an expression column.
Show such a value in various views, or use it in other expressions further? Use a field.