Legacy vs New Filter Gotcha | Community
Skip to main content
Doug_Den_Hoed__AtAppStore
Community Advisor
Doug_Den_Hoed__AtAppStoreCommunity Advisor
Community Advisor
September 18, 2023
Question

Legacy vs New Filter Gotcha

  • September 18, 2023
  • 1 reply
  • 559 views

 

This one's quite technical, but I decided worth mentioning.

 

For those of us who rely on the conventions Workfront uses in its Filter definitions, I invite you to note the following subtle change when the exact same filter is saved using either the New Filter or the Legacy Filter builder:

 

In my case, this change -- did I miss a memo? -- led to us "hardening" our Magic Reports solution logic today so that when a user selects the New Filter version, rather than it literally being interpreted (as it did 12 hours ago) as:

 

 

Status IN "HLD,DED"

 

 

And returning no data (since no Status matches the string "HLD,DED"), it is correctly applied (as it historically was using the Legacy Filter version) as

 

Status IN "HLD","DED"

 

 

Save until needed.


Regards,

Doug

 

 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    1 reply

    RandyRoberts
    Community Advisor
    RandyRobertsCommunity Advisor
    Community Advisor
    September 20, 2023

    Well IMO the entire filter experience is a mess. At least now the syntax is a little more consistent with standard syntax norms.

    I think Adobe needs a single person overseeing ALL Workfront filters from Workload Balancer assigned filters toWorkload Balancer unassigned filters to Boards filters, to reports filters, to planner filters, etc., etc. They all work differently and there is no governance over anything other than report filters.

    Plus, the stacking only stacks with "AND" not "OR". If I want projects in Planning OR Active I still need a separate filter for that as I cannot stack an Active and a Planning filter.

      Terms & ConditionsAccessibility statement

      Loading footer...