Differences Between DATANORM 4 and 5
Where DATANORM 4 and DATANORM 5 differ, and what that means for your imports.
Last updated
⌘Ctrlk
Where DATANORM 4 and DATANORM 5 differ, and what that means for your imports.
Article data
split across A record and B record
entirely in the A record
Additional details
EAN, match code, catalogue page, copper weight in the B record
contained in the A record
Units
free German abbreviations such as ST, Stck, M
ISO codes such as PCE, MTR
Price record
up to three articles per P record line
one article per line
Price notation
integer, decimals via the price indicator
explicit decimal notation
Text length
shorter fields
longer fields for descriptions
A DATANORM 4 file with 4,637 articles contains roughly 9,274 article lines, because each article consists of an A and a B record. Staging still shows 4,637 records. The merge is intentional.
A V4 price file with 9 lines can produce 25 price records, because one line carries up to three article blocks. Price staging holding more entries than the file has lines is therefore correct.
With DATANORM 4 you meet unit codes that need their own mapping more often. Initialize Units covers the widespread German abbreviations; add rare ones in the unit mapping.
The price indicator distinguishes list price (1) from net price (2). The app stores both in separate fields so they cannot overwrite each other. Which one becomes the purchase price is controlled by Purchase Price Source, see Purchase Price Lists.
On import the version is detected from the header record – nothing to configure.
On export you choose the version deliberately. The default comes from Default DATANORM Version in the setup and can be overridden in the wizard. See DATANORM Export.
For new data deliveries DATANORM 5 is the better choice: fewer record types, unambiguous units and clear decimal notation. DATANORM 4 remains supported because many suppliers still use it.
Last updated