[Vtigercrm-commits] [Vtiger development] #8360: Import Duplicate Handling (Step3) for Inventory Modules
Vtiger development
vtiger-tickets at trac.vtiger.com
Tue Dec 9 08:26:49 GMT 2014
#8360: Import Duplicate Handling (Step3) for Inventory Modules
-------------------------------------------------+-------------------------
Reporter: mathdesc | Owner: mathdesc
Type: known issue | Status: new
Priority: major | Milestone: Unassigned
Component: vtigercrm | Version:
Severity: High | Resolution:
Keywords: |
import,duplicate,invoice,salesorder, |
-------------------------------------------------+-------------------------
Comment (by mathdesc):
Replying to [comment:2 mathdesc]:
[...]
>
> To me if a group by clause has to be, it should rather be on creation
time.
> First because while allowing to name (subject) multiples invoice (which
is good a customer convenience) the same, it's non coherent then to import
& automerge on subject.
>
> Actually while relying on the Created Time to group by invoices, and as
multiple items lines within an invoice are created on the exact same date,
the result is correct.
>
> So finally without any Step3 handling nor duplicate handling but only
the group by clause fix on createdtime it does well.
>
>
Addendum:
The issue also impacts Salesorders and if my fix remedy their import as
well, fixed invoice import still have a subsequent issue :
2 or more salesorders named identically linked to different invoices are
not correctly discriminated. In other words, the invoice export process
only gives the salesorder name (and since it is allowed to have same
soname - which is again good for me), it's not enough to bound correctly
an invoice to its salesorder in the context of export/import.
Obviously again, the resolution involves the salesorders createdtime as an
additional column to its name (subject)
--
Ticket URL: <http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/8360#comment:4>
Vtiger development <http://trac.vtiger.com/>
Vtiger CRM
More information about the vtigercrm-commits
mailing list