From: Bernd Bleßmann <bernd@kivitendo-premium.de>
Date: Wed, 23 Oct 2013 10:48:05 +0000 (+0200)
Subject: Verwendung von datatype in der Doku deutlicher herausgestellt.
X-Git-Tag: release-3.1.0beta1~22^2~117
X-Git-Url: http://wagnertech.de/git?a=commitdiff_plain;h=fa7c3cb5774b65d53cd5f4cdbb9443ad7e8ac671;p=kivitendo-erp.git

Verwendung von datatype in der Doku deutlicher herausgestellt.
---

diff --git a/SL/Helper/Csv.pm b/SL/Helper/Csv.pm
index 1cc0fae5c..2730502b3 100644
--- a/SL/Helper/Csv.pm
+++ b/SL/Helper/Csv.pm
@@ -446,13 +446,17 @@ in objects.
 If not given, headers are taken from the first n lines of data, where n is the
 number of different class types.
 
+In case of multiplexed data the first column must be named 'datatype'. This
+name must be given in the header.
+
 Examples:
 
   classic data of one type:
   [ 'name', 'street', 'zipcode', 'city' ]
 
   multiplexed data with two different types
-  [ [ 'ordernumber', 'customer', 'transdate' ], [ 'partnumber', 'qty', 'sellprice' ] ]
+  [ [ 'datatype', 'ordernumber', 'customer', 'transdate' ],
+    [ 'datatype', 'partnumber', 'qty', 'sellprice' ] ]
 
 =item C<profile> [{profile => \%ACCESSORS, class => class, row_ident => ri},]
 
@@ -493,7 +497,8 @@ If C<class> is present, the line will be handed to the new sub of this class,
 and the return value used instead of the line itself.
 
 C<row_ident> is a string to recognize the right profile and class for each data
-line in multiplexed data.
+line in multiplexed data. It must match the value in the column 'dataype' for
+each class.
 
 In case of multiplexed data, C<class> and C<row_ident> must be given.
 Example: