OK, I may have to raise this in Bugzilla, but before I do, I will ask here. When staff price up items with a cost of replacement they need to edit both the $v field and the $w field because Koha does not know to change $w automatically when a change is made to $v. But Koha is silently demanding that data keyed in $w be in the YYYY-MM-DD format. If you key 2019-11-22 Koha will be happy with that and the data will save. But if you key 22-11-2019 (or any other date format) Koha will refuse to accept this data but will not warn. The SAVE operation will see this field cleared out and emptied (if there was something there previously), or left empty (if you are trying to key data into that field for the first time). We might alter the text in Basic constraints in the frameworks to warn the user what to do, but ideally the replacementpricedate would use a date picker, to ensure the item record field populates correctly. Anyone got any tips on how I can do this? Ray Delahunty University of the Arts London . This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY