Print

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

[rhom]

my IsEmpty problem:

yes i know that empty fields were changed ages ago to return "Unknown <field description>" during a rename.

my issue is that in previous (less than a month) builds IsEmpty used to return TRUE during a rename and i could use an expression to alter the path, now i can't because IsEmpty is returning FALSE (presumably because it's seeing the "unknown" value).

can it be put back to checking before the "unknown" value is created?  it worked the way (almost) everyone wanted and for those that didn't like that we could expression around it.

[Matt]

my IsEmpty problem:

yes i know that empty fields were changed ages ago to return "Unknown <field description>" during a rename.

my issue is that in previous (less than a month) builds IsEmpty used to return TRUE during a rename and i could use an expression to alter the path, now i can't because IsEmpty is returning FALSE (presumably because it's seeing the "unknown" value).

can it be put back to checking before the "unknown" value is created?  it worked the way (almost) everyone wanted and for those that didn't like that we could expression around it.

You may need to use IsEqual([Artist], Unknown Artist) in this tool.

[rhom]

but it's using the field's description (which in my library the Artist field's description is "Artist [Album]") and not it's actual name - just anther thing to make expressions harder to transport across users.

i change the field descriptions so they sort nicely in the tag window.