xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Item Group Rule — entity reference
REFERENCE · Last reviewed

Item Group Rule — entity reference

One clause of an item group's dynamic-membership predicate: a field name, an operator and a comparison value, applied in sequenceNumber order. The shared group-member rule engine translates clauses over real scalar Item columns into a parameterized SQL predicate and evaluates the remainder (custom fields, includes/excludes, custom logic) in memory, combining them according to the parent group's rule success criteria. Rules are only ever evaluated by the group's ProcessMembers action; editing a rule does not re-derive membership on its own.

Fields

FieldLabelTypeRequiredWhat it does
CreatedByCreated ByLookupYes
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
FieldNameField NameTextYesNames the property of Item the clause tests. A real scalar column is matched case-insensitively and pushed into SQL as a parameterized predicate; a custom-field name is resolved from the record's custom-field bag and evaluated in memory. A name that matches neither makes the clause pass unconditionally.
FieldValueField ValueTextThe comparison value, always stored as text and coerced to the target column's type. Numeric comparisons are scale-insensitive, so '10000.00' matches a stored 10000; in/notIn split it on commas and includes/excludes on semicolons.
IdIdGuidYes
ItemGroupIdItem GroupLookup → ItemGroupYes
LastModifiedByLast Modified ByLookupYes
ModifiedByIdModified ByLookup → UserAccountYes
NameRule NameText
OperationOperationPickListThe comparison the clause applies. The engine recognises equals, notEqual, lessThan, greaterThan, lessOrEqual, greaterOrEqual, like (contains), in and notIn (comma-separated), and includes/excludes (semicolon-separated, evaluated in memory). Anything unrecognised - including an empty value - falls back to equality, and the seeded picklist is both incomplete (no equals, like, in or includes) and entirely inactive.
OwnerIdOwnerLookup → UserAccountYes
RecordTypeIdRecord TypeGuid, hidden
SequenceNumberSequence NumberNumberYesAscending evaluation order of the clauses, and the numbering that the group's custom-logic expression refers to - clause one is the lowest sequence number.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
BulkDeleteDelete SelectedDeleteDelete the selected records.
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete in a list page
EditEditEditEdit
EditInLineEditEditDelete in page.
NewNewNewNew
UIActionUI ActionUIActionUI Action