Message 26088

Message id


2016-06-03 13:10 GMT+02:00 Cédric Krier <>:

> Cédric Krier <> added the comment:
> On 2016-06-03 12:51, Guillem Barba wrote:
> > The situation that motivated this issue is a cron that process lot of
> > invoices for lot of companies.
> > The error raised usually is a domain problem or a required field error.
> > These errors doesn't  show which record fail.
> > Without more information that "in some of the thousands invoices there is
> > one that field X is missing", it so hard to find which is the problematic
> > invoice.
> > To have the company that failed allows the user to reduce the invoices to
> > check.
> It does not sound like a real solution.

It works pretty well in our use case (the invoices are processed and committed in blocks of 20, so the user only need to check the first 20 of the reported company).
Any way, it was the solution available modifying less the core code (in 3.4 the patch was very easy because the send email action is done inside the context per company).

> > Another solution is to put the record rec_name in the domain/field required
> > error messages. Provably this solution will solve more UX problems.
> Yes that sounds like a better solution.
> But usually rec_name getter is considering that the record is valid. So
> maybe the id is better.

I change the name of the issue to do this improvement.
Date User Action Args
2016-06-03 13:25:37guillemNaNsetmessageid: <>
2016-06-03 13:25:37guillemNaNsetrecipients: + ced, resteve
2016-06-03 13:25:37guillemNaNlinkissue5581 messages
2016-06-03 13:25:36guillemNaNcreate

Showing 10 items. Show all history (warning: this could be VERY long)