# User mistakes when introducing dates in different forms
**URL:** https://discuss.tryton.org/t/user-mistakes-when-introducing-dates-in-different-forms/2738
**Category:** User
**Created:** [May 19, 2020, 2:40pm UTC](https://discuss.tryton.org/t/user-mistakes-when-introducing-dates-in-different-forms/2738 "2020-05-19T14:40:44Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@santi](https://discuss.tryton.org/u/santi)
#### Post date: [May 19, 2020, 2:40pm UTC](https://discuss.tryton.org/t/user-mistakes-when-introducing-dates-in-different-forms/2738/1 "2020-05-19T14:40:45Z")
We often find that users make mistakes when introducing dates and those mistakes are difficult to fix afterwards. For example, we find out:
- Sales with the wrong sale date (which cannot be changed with sale\_amendment). Having one or two sales in the future is a frequent mistake.
- Customers phone asking for somebody to modify a shipment they introduced in the wrong date. The wrong date here affects stock and shipments cannot be undone, it is frequently a problem quite annoying to solve.
I wonder how others are solving those problems.
Would it be a good idea a warning raised when those documents have “rare” dates? We should, of course, agree on what “rare” means.
Other ideas?
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [May 19, 2020, 3:10pm UTC](https://discuss.tryton.org/t/user-mistakes-when-introducing-dates-in-different-forms/2738/2 "2020-05-19T15:10:21Z")
> [@santi](#):
>
> Sales with the wrong sale date (which cannot be changed with sale\_amendment). Having one or two sales in the future is a frequent mistake.
Having wrong sale date for confirmed sale is no more a problem because it will no more be used.
> [@santi](#):
>
> Customers phone asking for somebody to modify a shipment they introduced in the wrong date. The wrong date here affects stock and shipments cannot be undone
A waiting customer shipment can be re-planned by going back to draft, change the planned date and set back to waiting.
---
### Author:  [@santi](https://discuss.tryton.org/u/santi)
#### Post date: [May 20, 2020, 10:32am UTC](https://discuss.tryton.org/t/user-mistakes-when-introducing-dates-in-different-forms/2738/3 "2020-05-20T10:32:48Z")
> [@santi](#):
>
> Customers phone asking for somebody to modify a shipment they introduced in the wrong date. The wrong date here affects stock and shipments cannot be undone
A waiting customer shipment can be re-planned by going back to draft, change the planned date and set back to waiting.
[/quote]
The cases that we are referring are customer shipments and supplier shipments which are already done. For example common case when speaking about supplier shipments:
- the user which receives the goods has to inform an expiry date to the product lot
- the expiry lot date is 10/10/2025
- after introducing the expiry date they introduce the effective date in the supplier shipment and finish the shipment, but the problem is that they have introduced 20/05/2025 instead of 20/05/2020.
After this point, there is no way back for the users.
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [May 20, 2020, 10:39am UTC](https://discuss.tryton.org/t/user-mistakes-when-introducing-dates-in-different-forms/2738/4 "2020-05-20T10:39:31Z")
Why filling the effective date? You can let the system put today automatically.
More over, we have now a confirmation for all non reversible actions but we need at some point have those actions.
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [May 20, 2020, 11:08am UTC](https://discuss.tryton.org/t/user-mistakes-when-introducing-dates-in-different-forms/2738/5 "2020-05-20T11:08:04Z")
> [@santi](#):
>
> they have introduced 20/05/2025 instead of 20/05/2020
Indeed there is no reason to allow stock move in the future so I filled [Prevent doing move in the future (#9355) · Issues · Tryton / Tryton · GitLab](https://bugs.tryton.org/issue9355).