![]() ![]() The two conjunctions available are "And" & "Or": You can logically connect conditions together, into a condition group, using conjunctions. This is where the ability to logically connect your conditions using a conjunction becomes invaluable. Using a combination of conditions is essential for filtering through your records to create valuable views. In any workflow, information requests are rarely as simple as, "Show me the chairs." More often, questions are complex and investigatory, combining different variables (i.e., "show me the chairs AND make sure the chairs are in stock") or different priorities (i.e., "show me the chairs OR tables"). You can easily rearrange conditions by clicking on the pull handle for that condition, then dragging and dropping it where desired: You can remove a condition from a view by clicking on the trash can icon next to that condition: This makes it more obvious that there's been a filter applied in the view you're currently using. When you're done setting the condition's field, operator, and comparison value, notice that the filtering field is now shaded with a light green color. Here is how quickly we set up that new condition in real-time: Summing that up, we want to set a condition to see records "Where the ": Value - finally, we enter the value, "Chairs," that our Type field needs to have the value of to meet this rule.Operator - we want to ensure the Type is "Chairs.".Field to be evaluated - the Type field is the field we mentioned in our new rule above.So our new rule will be something like, "A record must be of the chair type to be visible." Our condition breaks down easily into three parts: Trust us on this one! By spelling out your condition into a statement, it'll help crystallize which fields, values, and operators should be involved. For example you can make statements like "Where " or "Where. ![]() When you are figuring out a new condition you'd like to create, we recommend stating the rule you'd like to set as a sentence first. To add a new filtering condition in a view, start by clicking the "Filter" button, then clicking the "Add condition" button: We want to set a condition only to show the records that represent chairs in this table. Here we have a table with many types of furniture, with a field called Type that tracks the type of each piece of furniture: ![]() This eliminates the need for complex string-matching filters and leverage the full power of linked records in your filtered views. Note that operators "is empty" and "is not empty" do not require you to input a value because the default value is empty.ĭid you know?We added functionality that lets you filter off of specific linked records by using filter operators such as "is exactly", "has any of", "has all of", or "has none of" along with a linked record field. A value - This is the value you compare all of your records against- using the field you just specified.For example, text fields will have filter operators like "contains," "does not contain," "is empty," or "is not empty" number fields will have filter operators like "is greater than" or "is less than." Which filter operators are available is determined by the field type.An operator - After selecting a field, choose an operator from the pre-populated dropdown menu.You can create a condition to filter out records within the view you are currently viewing.Ī condition reads much like a sentence the example above can be read as: "Show me the records where the DRI is Jordan Peretz." For this guide, we will be using the "Product catalog" template please feel free to create a copy of the base if you'd like to follow along! Conditions One great example of how to use conditions is to archive old projects that are no longer relevant. You need to prevent people from seeing certain records in a view share link.You only need to focus on records that meet certain conditions (e.g., the records that have been assigned to me AND have not been marked as completed).You're trying to find a record or records that meet certain conditions quickly (e.g., records that have a due date after X date and before Y date).OverviewĪ condition is a rule you set that records must follow to be visible in that particular view. We also recommend reading the support article on advanced filtering to fullycustomize how your records are filtered by utilizing condition groups. This article will go over the basics of working with conditions. When a record is filtered out based on a condition, it is not deleted-it's just hidden from the particular view you're using to look at your table. One of the core features of views is the ability to filter out records from a view according to conditions you set. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |