INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Import Configuration Behavior: JRiver 29 vs. 33  (Read 175 times)

PreLives

  • Recent member
  • *
  • Posts: 10
Import Configuration Behavior: JRiver 29 vs. 33
« on: January 13, 2025, 11:05:58 am »

I recently upgraded from JRiver 29 to V33, and I've noticed a difference in how the import configuration works.

In V29, when assigning a value to a list field like [Keywords], the value would be added if the field was blank or appended if there was an existing value. However, in V33, the value is added when the field is blank but overwrites any existing value instead of appending to it. In V29, I used the checkbox option "Skip for files that already have a value in this field" to control assigning or overwriting a value.

Was this change intentional, or is it a bug? Personally, I preferred how this part of the import process worked in V29.

Below is an example of how my configuration functions. Essentially, it checks the [Name] field to see if a specific keyword exists. If the keyword is found, it’s assigned to the [Keywords] field. Then, the first keyword is removed from the [Name] field to allow the process to search for Keyword2, and so on.

Configuration Example:

Field: Keywords
Value: =IfCase([Name],8,Keyword1,Keyword1,Keyword2,Keyword2,Keyword3,Keyword3)
Field: Name
Value: =Replace([Name],ListItem([Keywords], 0),,1)

Field: Keywords
Value: =IfCase([Name],8,Keyword1,Keyword1,Keyword2,Keyword2,Keyword3,Keyword3)
Field: Name
Value: =Replace([Name],ListItem([Keywords], 1),,1)

Field: Keywords
Value: =IfCase([Name],8,Keyword1,Keyword1,Keyword2,Keyword2,Keyword3,Keyword3)
Field: Name
Value: =Replace([Name],ListItem([Keywords], 2),,1)
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42506
  • Shoes gone again!
Re: Import Configuration Behavior: JRiver 29 vs. 33
« Reply #1 on: January 13, 2025, 11:14:10 am »

It was an intentional change.

MC 30.0.42:
Changed: Tag on import rules now replace list type fields instead of appending to them.
Logged
Matt Ashland, JRiver Media Center

PreLives

  • Recent member
  • *
  • Posts: 10
Re: Import Configuration Behavior: JRiver 29 vs. 33
« Reply #2 on: January 14, 2025, 02:33:52 pm »

Could you share the rationale behind this decision?

List fields are inherently designed for multiple values, and the previous behavior in V29 seemed more intuitive. Users could easily clear or replace values with the Replace() function if needed, while the new behavior in V33 requires using the more complex ListBuild() function to append values.
Logged
Pages: [1]   Go Up