Supported DATANORM Versions
Which DATANORM versions are read, how detection works and how to recognise the files.
Last updated
⌘Ctrlk
Which DATANORM versions are read, how detection works and how to recognise the files.
DATANORM 4.0
yes
yes
Article data is split across an A and a B record that belong together.
DATANORM 5.0
yes
yes
All article details sit in the A record. Recommended version.
The version is determined from the header record (V record) as the file is read, so you never have to specify it.
The Default DATANORM Version setting only applies to export. For import, the value in the file always wins.
In DATANORM 4 an article is described across two lines: the A record carries description, price and unit, the B record carries additional details such as EAN, match code, catalogue page or copper weight. Both belong to the same article number.
The app merges the A and B record into one staging record. A file with 4,637 articles therefore produces 4,637 staging rows, not 9,274.
In DATANORM 5 those details are already in the A record; there is no B record.
The full comparison is under Differences Between DATANORM 4 and 5.
A DATANORM delivery usually consists of several files with meaningful extensions:
DATANORM.001, DATANORM.002 …
Article data. Numbered sequentially for large catalogues.
DATPREIS.001
Price change only, for articles already delivered.
*.RAB
Discount groups.
*.WRG
Product groups.
Only read a price change file after the matching articles have been imported. Otherwise the price records have no article to attach to.
DATANORM files are traditionally DOS-encoded (code page 437/850). The app reads them accordingly so that umlauts in article descriptions arrive intact. Do not open and save a file as UTF-8 in a text editor before importing it – that loses the umlauts.
Last updated