Skip to main content

Apply filters

Follow

Comments

8 comments

  • METER Group

    On the operand section,

    When set to 'Field' I want to know why no field values appear in the picklist.  For example in my custom flow when I have the filter in my previous lookup set to the variables I intend to use (actually, I'm not sure whether that is related).

    I need to know when to use 'value', and when to use 'expression'.  I have a response mapped field  called K_data (mapped from data), and the filter doesn't work when I set the operand type to 'value', but it does for 'expression'.  Why?  

    Comment actions Permalink
  • METER Group

    In the section "Navigating the filter editor", in the first picture, is 'NOT' enable or is 'NOT' disabled?

    Comment actions Permalink
  • METER Group

    I'm 99% certain the picture is the opposite of the text, and the text is wrong.  The default when creating a new filter appears to be to have NOT enabled.

    Comment actions Permalink
  • METER Group

    Another thing that would be extremely helpful would be to describe the syntax/formating for the various Operand Type options.  Do I need to put Operands in quotes  (e.g. "Opp_data"), and does that answer change based on the Operand Type?  What about the values that I'm looking for (the right side or RVALs)? Do they need to be open? in single quotes? in double quotes?  and does the type of single quote matter like it does in SOQL queries where I can't paste in the fancy curved single quotes that a Google Doc generates? (That is a terrible thing to have to debug, by the way. I edited my query in a google doc and pasted it into the SOQL query window and spent a full day trying to figure out that it wouldn't work because google doc only allows you to type curved quotes, and the query ONLY understood straight ones).

    Can I put in an array name to see if 'is empty', or can I only put in individual values (array[0].member)? and, how do I format a member?  array.member?  array.0.member?  array[0].member?

    Comment actions Permalink
  • METER Group

    It would also be good to explain that I can paste a JSON file into the Input window, and use it to test my filter.  and that I can get that json file from Retry Data.

    Are there any funny things about it? Do I need to save the filter each time I change it before I click on the 'Preview' button? Do I need to recreate the filter each time I edit the Input data?

    This may seem obvious to you, but it was not obvious to me, and I lost a lot of time testing the hard way.

    Comment actions Permalink
  • METER Group

    Note, that these comments were all  made  in reference to the new UI.

    One place I have noticed that this is relevant is that the Legacy UI actually defaults to have the NOT disabled for input filters.

    Comment actions Permalink
  • METER Group

    You mention the option of creating a javascript filter, but then you don't give any guidelines on how to save that javascript filter.  If this is not the best document for that information, then please put in a link that tells about creating js files and functions.

    Comment actions Permalink
  • Tom Santiago

    Hi METER Group,

    Thanks for all of this feedback on filters:

    • I've revised the article to explain that the NOT filter is actually enabled by default in the current UI, thanks for bringing this to our attention.
    • In testing, with a string value equals operator, no quotes, single quotes, or double quotes all produced the same results and the behavior of the filter operated as expected. Do not use smart quotes.
    • When accessing an array, I was able to successfully create an "is empty" filter using the syntax arrayName.0, but I am still researching the nuances of when to use alternate array referencing syntax (arrayName[0] for instance). I will revise this article according to my findings. 
    • We have an initiative to make our JavaScript content more robust throughout the knowledge base. I'll make sure to notify you of new content on that front as it occurs.

    Our Support team will be contacting you soon about the other issues you've brought up. This is great feedback, Kenneth. Thanks for your patience while we address the rest of your concerns.

    Comment actions Permalink

Please sign in to leave a comment.