Print

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

[andrewt]

I wasn't sure how to title this, so please bear with me if I got the terminology wrong...

Can MC assign a value to one field based on the value of another field? Example: I type "Bach, Johann Sebastian" into the "composer" field, and MC writes "Germany" in the "country" field. Of course I would have to make a list of some sort to tell it what to do. Can this be done?

[vagskal]

It is possible but it is a bit ugly.

Make two new custom fields:
ComposerCountry: User data field (Where you input the Country information)
ComposerCountryINTERNAL: Calculated data with this expression: If(IsEmpty([ComposerCountry]),,Save([ComposerCountry],varComposerCountryListItem([Composer],0),1))

In a view with columns display those two fields in columns. The second field should show the correct Country info for the primary (first) composer, if entered once for that composer in the ComposerCountry field.  You could also add an expression column with this expression to show the Country info: Load(varComposerCountryListItem([Composer],0))

In the rules for file display for that view enter this: ([ComposerCountryINTERNAL]=[] or -[ComposerCountryINTERNAL]=[])

This worked for me when I tried it a while ago when the global variables were developed. I have not tried it with recent builds.

[MrC]

Since you are going to enter the country / artist at least once, would it be an option to create a relational (one value / artist) Artist Country field?  You'd set country once for each artist (or composer, or ...).

[vagskal]

Since you are going to enter the country / artist at least once, would it be an option to create a relational (one value / artist) Artist Country field?  You'd set country once for each artist (or composer, or ...).

Yeah, it would certainly be easier if fields could be made relational to the Composer field, not just the Artist, Album and Series fields...