Dimensions No Longer Mapped to Merge Field Collections

Dimensions sent with postings to a connected financial system are defined by mapping them to document merge fields. An example:

However, OutgoingDeliveryLines is a collection of lines so it does not give 1 value but multiple values. A dimension should always be mapped to a single value to be useful for the grouping of data in the financial system. In fact if a dimension has more than 1 value, a connected financial system like Navision may reject it.

Thus from version 3.16.0 onward, new dimensions have been created that allow users to map dimensions to the correct single value without using collection merge fields. Further, to avoid problems if a dimension is mapped to a merge field that contains more than one value, that dimension will always remain empty when it returns more than one value.

Several new merge fields have been created to replace dimensions mapped to collections. These are:

Dimension	Current merge field	New merge field (red is new)	Notes
PRODUCTGROUP	Logistics.OutgoingDeliveryLines.Cargo.Specification.Commodity	LogisticsDeliveryLine.IncomingCargo.Specification.Commodity	Instead of 1 Cargo property with varying content there are now 2 to separate incoming/outgoing.
PRODUCTGROUP	Logistics.OutgoingDeliveryLines.Cargo.Specification.Commodity	LogisticsDeliveryLine.IncomingCargo.Specification.Commodity	Instead of 1 Cargo property with varying content there are now 2 to separate incoming/outgoing.
DELIVERY	Logistics.DeliveryNr	LogisticsDelivery.DeliveryNr	Use LogisticsDelivery instead of Logistics to support all cases.
CONTRACT	Logistics.Contract.ContractNo	LogisticsDelivery.Contract.ContractNo	Use LogisticsDelivery instead of Logistics to support all cases.
ORIGIN	Logistics.IncomingDeliveryLines.Cargo.Specification.Origin	LogisticsDeliveryLine.OutgoingCargo.Specification.Origin	Instead of 1 Cargo property with varying content there are 2 to separate incoming/outgoing.
P-CONTRACT	Logistics.IncomingDeliveryLines.SourceLot.ContractNo	LogisticsDeliveryLine.SourceLot.ContractNo	A user selects the right line automatically.
PRODUCTGROUP	Logistics.IncomingDeliveryLines.Cargo.Specification.Commodity	LogisticsDeliveryLine.OutgoingCargo.Specification.Commodity	Instead of 1 Cargo property with varying content there are 2 to separate incoming/outgoing.
TRANSPORT	Logistics.Transport.TransportNr	LogisticsDelivery.Transport.TransportNr	Use LogisticsDelivery instead of Logistics to support all cases.
CONTRACT	Logistics.Contract.ContractNo	LogisticsDelivery.Contract.ContractNo	Use LogisticsDelivery instead of Logistics to support all cases.
DELIVERY	Logistics.IncomingDeliveryLines.DestinationLot.DeliveryLineNo	LogisticsDeliveryLine.DestinationLot.DeliveryLineNo	This selects the right line automatically.

Note: On InvoiceLines, Logistics. now becomes obsolete and references to it will be removed from the document generation manual. Instead Agiblocks will add LogisticsDelivery to be the relevant endpoint of the invoice line. LogisticsDeliveryLine will take its line from there instead of from the old Logistics property.