xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse 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
Auto DMSConsumer Goods DMSSales Force Automation (SFA) 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/Conversion Definition — entity reference
REFERENCE · Last reviewed

Conversion Definition — entity reference

A conversion definition is the setup record that declares one bulk document conversion, for example order to invoice, for the Bulk Conversion screen and its conversion batches. It names the source document and its lines, the document created, the source-line quantity that is consumed and the pool it is reserved in, the server actions that stage a batch and convert each record, how failures are contained, and what the screen shows. A conversion exists only while an active, complete definition exists for it; there is no built-in fallback. Definitions are tenant setup data, none are seeded, and they are kept in the Sales app under Settings, Conversions. On a new definition, choosing the source entity and the record action fills every other blank field that the action implies; values already entered are never replaced.

Fields

FieldLabelTypeRequiredWhat it does
BatchActionNameBatch Action NameTextYesThe server action on the source entity that stages a batch. A definition naming an action makes that action batch-based. Picked from the source entity's server actions; on a new definition it defaults to the record action.
CategoryCategoryTextFree-text grouping, for example Sales or Procurement. Conversions are listed in category order; it has no effect on how a conversion runs.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated OnDateAndTimeYes
DefaultChunkSizeChunk SizeNumberLines per execution transaction, copied to each batch when it is staged. Default 50. A chunk always takes whole records, so a record with more lines than this is still processed in one chunk.
DefaultMaxAttemptsMax AttemptsNumberWhole-batch attempts a batch gets before it stays Failed, copied to each batch when it is staged. Default 3.
DefaultMaxLineAttemptsMax Line AttemptsNumberAttempts each batch line gets for unexpected errors before it is parked as Failed, copied to each batch when it is staged. Default 3. A parked line releases its reservation.
DescriptionDescriptionLongMultiLineTextExplanatory text shown under the Bulk Conversion screen title.
FailureIsolationFailure IsolationTextHow much one failing record takes down with it. ChunkThenRecord (default): run the chunk in one transaction and, if it fails, re-run it one record at a time so only the bad record fails. Record: one transaction per record. Chunk: all or nothing per chunk. A record refused by validation fails on its own in every mode.
IdIdGuidYes
IsActiveActiveBooleanSwitches the conversion on or off. An inactive definition is ignored entirely: the screen shows Conversion not available, new submissions fail, and existing batches for the key can no longer run or be retried until it is reactivated.
LabelDisplay NameTextYesThe name users see on the Bulk Conversion screen and on batches. Left blank on a new definition, it is suggested from the source and target, for example Order → Invoice.
LegacyActionNamesLegacy Action NamesLongMultiLineTextNot stored and not used.
LineFieldsLine FieldsLongMultiLineTextThe line fields shown as columns on the screen's lines tab, picked from the line entity's fields. Every Selection Field must also be listed here to have a column to edit.
ListFieldsList FieldsLongMultiLineTextThe source-document fields shown as columns on the screen's records tab, picked from the source entity's fields. Display only.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYesThe conversion key, a stable identifier such as sales.order-to-invoice. Screens and batches refer to the conversion by this key and look it up again when a batch runs or is retried, so renaming it stops existing batches from running or being retried. Left blank on a new definition, it is suggested from the source and target, for example order-to-invoice.
OptionsJsonOptions (JSON)LongMultiLineTextThe options users choose on the Bulk Conversion screen and that are passed to the action, edited as a table of Name, Label, Kind (Text, Boolean, Number or Choice), Choices and Default. On a new definition, options the action reads are filled in. Malformed content is ignored rather than refused.
OwnerIdOwnerLookup → UserAccountYes
PendingQuantityFieldPending Quantity FieldTextYesThe numeric field on the source line holding the quantity still to convert, for example the pending invoice quantity on an order line. Available quantity is this value minus what open batch lines in the same pool already hold; a line at zero or less is staged as Skipped.
QuantityPoolQuantity PoolTextThe name of the reservation pool the conversion holds quantity in. A batch cannot be staged without it. Conversions that consume the same pending-quantity field on the same line entity must share one pool name, or each sees the full quantity and the same units can be promised twice. Suggested as Source.Target, for example Order.Invoice, on a new definition.
RecordActionNameRecord Action NameTextThe server action on the source entity that converts one source record, for example the action that creates an invoice from an order. The batch runs it once per record with that record's staged lines. Picked from a list of the source entity's active server actions; on a new definition, choosing it fills every blank field the action implies. Without it staging works but every batch line fails.
RecordTypeIdRecord TypeGuid, hidden
ScopeFieldsScope FieldsLongMultiLineTextThe filters the Bulk Conversion screen shows, in order, picked from the source entity's fields. Lookup fields become pickers and date fields become a date range. Blank uses the standard set of the fields the source entity has. Filters only narrow what is offered; they are not stored on the batch.
SelectionArgsKeySelection Args KeyTextYesThe argument name that carries the picked lines to the conversion action, for example OrderLines. When the user picks individual lines the batch converts only those, at the quantities picked; otherwise every line with quantity available is converted. Both kinds of batch send their lines to the action under this name.
SourceEntitySource EntityTextYesThe internal name of the document converted from, for example Order. Picked from a list of entities. Choosing it fills blank Scope Fields and List Fields with the standard fields the entity has and lets the action fields list that entity's server actions.
SourceLineEntitySource Line EntityTextYesThe internal name of the source document's line entity, for example OrderLine. Filled from the line collection when left blank on a new definition. Choosing it fills a blank Pending Quantity Field and Line Fields from the line's fields.
SourceLineNavigationSource Line NavigationTextYesThe exact name of the collection on the source document that holds its lines, for example OrderLines. Staging loads the lines through it, so it must be the internal property name, not a label.
SourceLineParentFieldSource Line Parent FieldTextYesThe field on the line that points back to its header, for example OrderId. Filled from the entity model when left blank on a new definition.
SubscriptionKeySubscription KeyGuid, hiddenYes
TargetEntityTarget EntityTextYesThe internal name of the document created, for example Invoice. A record whose action runs without error but creates no record of this entity has its lines marked Skipped. The automatic fill cannot always find it, for example when the action creates the document through another service; set it by hand then.
TargetLineEntityTarget Line EntityTextThe internal name of the created document's line entity, for example InvoiceLine. Optional; suggested from the target entity on a new definition.
UpdatedDateTimeUpdated OnDateAndTimeYes