Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

kim_purcell
Kilo Explorer

If you are creating a record from a filtered list, you'll notice that some fields on the record automatically populate based on the filter conditions. For example, if the filter on the Incident list is [Priority] [is] [1 - Critical] and you click New, the Priority field automatically updates. Here's what your new incident will look like:

Priority Critical.jpg

If you are using filter conditions with the = operator, all of your values with the = are taken by default when you click on the New button. This is an enhanced feature and designed to behave this way. If you remove the =, this will prevent these value from populating.

Knowing how to add or remove the right filter conditions can help you set the correct default values when creating a new record. To keep in check the different ways to set your conditions, follow the guidelines below.

How to set filter conditions:

  • The current filter is a hierarchical list of conditions, also know as breadcrumbs, at the top of your table.

left to right conditions.jpg

  • Breadcrumbs are ordered from left to right, with the far left condition being the most general and the far right condition being the most specific.
  • Clicking a breadcrumb removes all of the conditions to the right.

Breadcrumb.JPG

  • Clicking the condition separator (>) before a condition removes only that condition.

Separator condition.JPG

Finally, clicking, ALL on a table the table above, for example, removes all conditions and returns all incidents in the system. Use this to ensure certain fields are not   auto-populated when creating a new record.

For related links, see:

Using Filter and Breadcrumbs

New button takes default value

2 Comments