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/Account Group — entity reference
REFERENCE · Last reviewed

Account Group — entity reference

A named set of Accounts used as a targeting dimension by the pricing, discount, tax, scheme, item-component and incentive engines: instead of naming each account, a PriceList, DiscountGroup, TaxGroup, Scheme, SchemeCondition, SchemeAccountBudget, ItemComponent, KPIConfiguration or IncentivePlan row points at a group and the engine resolves the accounts through AccountGroupMember. AccountGroupType partitions groups by which engine may consume them and each engine matches it as an exact string, so a group typed for one engine is invisible to the others. Membership is either maintained by hand as AccountGroupMember rows or rebuilt from the child AccountGroupRule rows, the latter through the group's Process Member server action. Groups are referenced separately in customer and partner roles (for example DiscountGroup.CustomerAccountGroupId versus PartnerAccountGroupId), so one group can scope either side of a transaction.

Fields

FieldLabelTypeRequiredWhat it does
AccountGroupTypeAccount Group TypePickListYesWhich engine may consume this group, matched as an exact case-sensitive string by the consuming service. The pricing engine looks for 'Price', discounts for 'Discount', tax for 'Tax', and the scheme engine for 'Scheme' and 'Exclude Scheme'. The seeded picklist does not currently offer 'Tax' or 'Scheme', and offers 'Incentive' and 'Item Feature' which no engine matches on (incentive plans and item features reference a group by foreign key instead), so the picklist and the engines disagree in both directions - check the stored value, not the option list. Values: Discount, Incentive, Item Feature, Price, Exclude Scheme, Tax.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DescriptionDescriptionText
DynamicMemberTypeDynamic Member TypePickListHow the member rebuild sources its accounts. Values: Field Filter.
ExternalIdExternalText
IdIdGuidYes
ModifiedByIdModified ByLookup → UserAccountYes
NameNameText
OwnerIdOwnerLookup → UserAccountYes
RecordTypeIdRecord TypeGuid, hidden
ReportIdReportText
RuleSuccessCriteriaRule Success CriteriaPickListHow the child rules are combined during a member rebuild. An empty value is treated as 'no criteria' and matches every account. Values: Any Rule Is Met.
RuleSuccessCustomLogicRule Success Custom LogicTextA boolean expression over the child rules referenced by their 1-based sequence position, used only when the criteria is set to custom logic; that combination forces the whole rebuild to evaluate in memory rather than in SQL.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
BulkDeleteDeleteDeleteDelete the selected records.
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete in a list page
EditEditEditEdit
EditInLineEditEditInlineDelete in page.
EditInListEditEditEdit
EditListHeaderEditEditInlineEditListHeader
NewNewNewNew
ProcessMembersProcess MembersServerAction (ProcessMembers, async)ProcessMembers
UIActionUI ActionUIActionUI Action

Validations

ValidationApplies toError messageNotes
Rule Success Criteria ValidationErrorSelection of Rule Success Criteria is mandatory if the Dynamic Member Type is Field Filter!Rule Success Criteria is mandatory in case of field filters.