Barend wrote: |
Stefan/Andreas,
When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."
The configuration file uses:
Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.
As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.
But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.
Is this a bug -or- do I have to change the configuration?
Thanks & regards, Barend
|
Hi Barend,
I can reproduce your point.
I've found various work-arounds, but possibly the best one is to remove "Audit Date" and "Deadline" from the Required Attributes line. True you won't get a warning saying that they were not entered for the first entry (if you didn't enter them, that is), but all subsequent replies run as you would want.
Another way is if you *preview* your entry, you can then submit it and that works. This seems to work by bring up a different page where you can edit all those Fixed Attributes. (I'm not sure that Preview is meant to do that, but it does and it's a work-around).
Or, if you remove "Audit date" and "Deadline" from the Fixed Attributes Reply (as you did) seems to work in the same way. But I see that you don't want the opportunity for these to be changed.
I note that if you get this error message and go back, the message that you may have written is erased (this is unusual, it doesn't do this if you have not supplied an attribute on the first entry, say).
So I suspect this is a bug, possibly not detected before; perhaps no-one had tried this combination. |