Products (Catalog)
Catalog/Product configuration aggregating both base product and variants mapping configuration.
"Catalog": {
"catalogStructure": {
"subCatalog": "",
"filePrefix": "Litium Export-Released products",
"exportId": ""
},
"mapping": {
"product": {
"root": "ECORESRELEASEDPRODUCTV2ENTITY",
"productArticleNumberSuffix": "-P",
"fieldTemplateId": "ProductWithVariants",
"taxClassId": "TaxClassId",
"articleNumberNodeName": "ITEMNUMBER",
"fields": [
{
"fieldDefinitionId": "_name",
"fieldDataNodeName": "SEARCHNAME",
"culture": "en-US",
"type": "string"
}
]
},
"variant": {
"root": "ECORESRELEASEDPRODUCTV2ENTITY",
"unitOfMeasurement": "UOM",
"articleNumberNodeName": "ITEMNUMBER",
"fields": [
{
"fieldDefinitionId": "_name",
"fieldDataNodeName": "SEARCHNAME",
"culture": "en-US",
"type": "string"
}
]
}
},
"importBatchSize": 500,
"defaultVariantFieldTemplate": "ProductWithVariants_default",
"defaultBaseProductFieldTemplate": "ProductWithVariants_base_default",
"defaultTaxClassId": "TaxClassId_default",
"defaultUnitOfMeasurement": "UOM_default",
"autoGenerateBaseProduct": false,
"generateUrl": false,
"urlFieldList": [],
"importBehavior": "proceedWithErrors"
},
defaultBaseProductFieldTemplate: string: default Litium product template
defaultTaxClassId: string: default class tax id
defaultUnitOfMeasurement: string: default unit of measurement
autoGenerateBaseProductbool: catalog import setting: Erp 1.1 reference
generateUrlbool: catalog import setting: Erp 1.1 reference
urlFieldList: string[ ]: fields for generating urls​
importBehavior: string: catalog import setting: Erp 1.1 reference [stopOnAnyError, proceedWithErrors]
catalogStructure
Containing information of product import structure.
subCatalog: string: product import sub catalog. If set the file prefix check will not be checked and all files will be treated as product files
filePrefix: string: file prefix for recognizing catalog import files. Only used when sub catalog is not set.
exportId guid: D365 export Id containing catalog files (Export-Released products)
Mapping
Mapping configuration for both Litium variants and base products.
Product
root: string: Root node of base product entity in catalog export file
productArticleNumberSuffix: string: suffix for differ base product from variant ID in case of 1 to 1 relation
fieldTemplateId: string: Litium product template id
taxClassId: string: Litium tax class Id
articleNumberNodeName: string: article number node name
articleNameNodeName: string: article name node
fields: string: array if fields mapping containing Litium FieldId, corresponding node in entity, Culture and type check Litium ERP 1.1 for reference.
Variant
root: string: Root node of variant entity in catalog export file
unitOfMeasurement: string: Node name for variant unit of measurement.
articleNumberNodeName: string: article number node name
articleNameNodeName: string: article name node
fields: string: array if fields mapping containing Litium FiledId, corresponding node in entity, Culture and type check Litium ERP 1.1 for reference.
Customer Import
Setting for organization and Persons import.
"Customer": {
"catalogStructure": {
"subCatalog": "",
"filePrefix": "Customers V3",
"exportId": ""
},
"defaultPersonFiledTemplate": "B2CPersonTemplate",
"defaultOrganizationFiledTemplate": "OrganizationTemplate",
"importBatchSize": 500,
"importBehavior": "proceedWithErrors",
"mapping": {
"customerTypeNodeName": "PARTYTYPE",
"discountPriceGroupIdNodeName": "DISCOUNTPRICEGROUPID",
"organization": {
"vatRegistrationNumberNodeName": "LINEOFBUSINESSID",
"legalRegistrationNumberMappingNode": "PRIMARYCONTACTPHONERECORDID",
"customerTypes": ["Organization", "LegalEntity"],
"idNodeName": "CUSTOMERACCOUNT",
"nameNodeName": "NAMEALIAS",
"fieldTemplateId": "OrganizationTemplate",
"defaultAddressType": "billing",
"fields": [
{
"fieldDefinitionId": "_name",
"fieldDataNodeName": "NAMEALIAS",
"culture": "en-US",
"type": "string"
}
],
"addressFields": [
{
"addressTypeId": "Billing",
"addressFields": [
{
"fieldDefinitionId": "Address2",
"fieldDataNodeName": "ADDRESSSTREET",
"culture": "en-US",
"type": "string"
}
]
}
]
},
"person": {
"customerTypes": ["Person"],
"idNodeName": "CUSTOMERACCOUNT",
"fieldTemplateId": "B2CPersonTemplate",
"fields": [
{
"fieldDefinitionId": "_firstName",
"fieldDataNodeName": "NAMEALIAS",
"culture": "",
"type": "string"
}
],
"addressFields": [
{
"addressTypeId": "Delivery",
"addressFields": [
{
"fieldDefinitionId": "Address1",
"fieldDataNodeName": "ADDRESSSTREET",
"culture": "en-US",
"type": "string"
},
{
"fieldDefinitionId": "City",
"fieldDataNodeName": "DELIVERYADDRESSCITY",
"culture": "en-US",
"type": "string"
}
]
}
]
}
}
},
defaultPersonFiledTemplate: string: default filed template
defaultOrganizationFiledTemplate: string: default organization template
importBatchSize: integer: number of customer/ organization imported in one batch
importBehavior: string: catalog import setting: Erp 1.1 reference [stopOnAnyError, proceedWithErrors]
discountPriceGroupIdNodeName: string: mapping for customer pricelist (In case of organization) and price group id (in case of persons).
catalogStructure
Containing information of product import structure.
subCatalog: string: customer import sub catalog. If set the file prefix check will not be checked and all files will be treated as product files
filePrefix: string: file prefix for recognizing catalog import files. Only used when sub catalog is not set.
exportId: guid: D365 export Id containing customer files (Customer V3).
mapping
Mapping configuration for both Litium Persons and Organization.
customerTypeNodeName: guid: Root node for customer mapping
Organization
vatRegistrationNumberNodeName: string: vat node name
legalRegistrationNumberMappingNode: string: legal registration node number
customerTypes: string[]: customer types mapped to organizations “Organization”, “LegalEntity”
idNodeName: string: Organization id node
nameNodeName: string: Organization name node id
fieldTemplateId: string: Organization template Id in Litium
defaultAddressType: string: Default address import type in Litium
fields: string: array if fields mapping containing Litium FieldId, corresponding node in entity, Culture and type check Litium ERP 1.1 for reference.
person
customerTypes: string[]: customer types mapped to organizations : “Person”
idNodeName: string: Organization id node
fieldTemplateId: string: Person template Id in Litium
fields: string: array if fields mapping containing Litium FieldId, corresponding node in entity, Culture and type check Litium ERP 1.1 for reference.
addressFields
Array of addresses mappings.
addressTypeId: string: Litium address type for mapping : ex: “Delivery”.
addressFields: array: Array if fields corresponding with Litium address model.
"addressFields": [
{
"fieldDefinitionId": "Address1",
"fieldDataNodeName": "ADDRESSSTREET",
"culture": "en-US",
"type": "string"
},
Inventory
"Inventory": {
"catalogStructure": {
"subCatalog": "",
"filePrefix": "Litium Export-Inventory on-hand by site",
"exportId": ""
},
"importBatchSize": 100,
"mapping": {
"defaultInventoryId": "Accelerator",
"inventoryIdNodeName": "INVENTORYSITEID",
"quantityNodeName": "TOTALAVAILABLEQUANTITY",
"articleNumberNodeName": "ITEMNUMBER"
}
},
importBatchSizeinteger: number of inventory items imported in one batch
catalogStruture
Containing information of inventory import structure.
subCatalog: string: inventory import sub catalog. If set the file prefix check will not be checked and all files will be treated as Inventory import files
filePrefix: string: file prefix for recognizing catalog import files. Only used when sub catalog is not set.
exportId: Guid: D365 export Id containing inventory files (Export-Inventory on-hand by site).
mapping
defaultInventoryId: string: Litium inventory id
inventoryIdNodeName: string: Inventory Id node name if not presented default will be used
quantityNodeName: string: Quantity node id
articleNumberNodeName: string: article number node id
Price import
"Price": {
"catalogStructure": {
"subCatalog": "",
"filePrefix": "Sales price agreements",
"exportId": ""
},
"importBatchSize": 500,
"importBehavior": "proceedWithErrors",
"mapping": {
"rootNode": "SALESPRICEAGREEMENTENTITY",
"vatIncluded": false,
"basePriceListId": "usdPriceList",
"defaultCurrency": "USD",
"currencyNodeName": "PRICECURRENCYCODE",
"customerIdNodeName": "CUSTOMERACCOUNTNUMBER",
"minQuantityNodeName": "SALESPRICEQUANTITY",
"articleNumberNodeName": "ITEMNUMBER",
"priceNodeName": "PRICE",
"priceCustomerGroupCode": "PRICECUSTOMERGROUPCODE"
}
},
mapping
rootNode: string: Litium inventory id
vatIncluded: string: indicating whether import file contains prices with VAT or not
basePriceListId: string: Default Litium accelerator price list if not presented in export file
defaultCurrency: string: Default Litium accelerator currency if not presented in export file
currencyNodeName: string: Node name for extracting currency
customerIdNodeName: string: Node name for extracting customer id for customer specific price lists
minQuantityNodeName: string: Node name for extracting minimum quantity
articleNumberNodeName: string: Node name for extracting Item id
priceNodeName: string: Node name for extracting Price
priceCustomerGroupCode: string: Node name for extracting price list name
catalogStructure
Containing information of inventory import structure.
subCatalog: string: inventory import sub catalog. If set the file prefix check will not be checked and all files will be treated as product files
filePrefix: string: file prefix for recognizing catalog import files. Only used when sub catalog is not set.
exportId: Guid: D365 export Id containing inventory files (Export-Inventory on-hand by site).