Metadata Filter Usage

metadata filters in licensespring allow you to search and narrow down entities (licenses, products, customers, orders, etc ) based on the custom metadata attached to them this provides a flexible and powerful way to manage and find relevant information directly within the platform without needing api calls supported pages metadata filters can be applied on license filter licenses by activation date, type, or custom tags license manager filter licenses by user or role metadata license users find license users based on license or user metadata customer search customers by preferences, region, or custom identifiers customer accounts filter customer groups by account level metadata products filter products by version, release date, or custom attributes orders search orders by source, payment type, or special instructions metadata filters panel use the metadata filters panel to create and apply metadata based filters main fields path metadata key (e g , customer region) operator comparison type (equals, contains, etc ) value value to match (e g , "production") type data type (string, number, boolean, object, array, null) + add filter add multiple filters to refine results preview see filters before applying actions apply or clear filters advanced mode enable complex queries filter types supported metadata types with examples string metadata customername="acme corp" number metadata maxusers=100 boolean metadata istrial=true null metadata assigneduser=null object metadata deployment environment="production" array metadata tags="keyaccount" for full json format examples of metadata filtering (including nested objects, arrays, numbers, booleans, and null values), see the “metadata filtering” section of the licensespring management api documentation advance mode filter syntax advanced mode filter syntax in advanced mode , you can enter metadata filters as a raw query string using metadata formatted keys filters follow a key value structure, where keys match metadata fields and values match stored metadata nested objects use double underscores ( ) to navigate deeper levels multiple filters are combined with and logic enter metadata filters as a raw query string, using metadata formatted keys example raw query metadata deployment environment="production" and metadata istrial=true this mode is ideal for complex queries or when you want to enter multiple filters quickly when advanced mode is enabled and you enter a raw query string, the panel will automatically populate the corresponding filter fields this makes it a useful reference for understanding how your query translates to individual filters once the fields are populated, the preview section will display the raw query for verification before applying the filters tips & best practices check metadata keys use the exact key names as defined in your metadata json case sensitivity metadata keys and string values are case sensitive preview before applying use the preview panel (if available) to confirm filter results before applying them use objects carefully filtering on nested objects requires the full path in key format