Yet I can export the ID of almost any record.
If CSV import is just meant to be a tool to import raw data, wouldn’t it be rather more sensible if one could (if one wanted to) use internal IDs to precisely and explicitly import just the data one wants to import? Naturally this would also require code to handle updating records through CSV imports, rather than just creating new ones.
Besides, the invoice import seems a bit weird nevertheless. The CSV import dialog asks for an Invoice Address field, but will only actually accept a Party Code. That doesn’t quite seem right.
This I wholeheartedly agree with. This is just the way it should be.
Yes. Scripting, or rather, a set of full fledged Tryton modules is definitely our endgame. However, due to, well let’s call them ‘various business reasons’ that goal won’t be happening in a day, or even a year. Not even if said Tryton modules already existed.
So for now, we’ll be stuck with getting the data we need from various sources, and putting it together in, well, Excel unfortunately. Lucky for us, we only need import it to Tryton 1-4 times a year for invoicing. Thus, a CSV import is actually a fairly functional workflow for now.
Also, when we do import the invoices, we import thousands of them at once. So any non-bulk solution would not work.