It would be very helpful for the admin to be able to set a "required" flag on fields in the UI to enforce data entry users to supply all necessary information.
by: Joe C. | over a year ago | General Enhancements
Comments
Absolutely. All too often important info such as customer/vendor address, contact details etc etc are omitted by users.
Second that!
I completely agree
A "must have". It will prevent orders being shipped without ship-to addresses.
I agree as well. We have to customize this into the UI. Not the kind of customizations I want to see.
ability to attach validation rules would be a plus
Completely agree. Needed for data entry - e.g. the Tax group field in AP miscellaneous payments when you don't select a vendor.
"required" flag on fields in the UI to enforce data entry -- is a MUST
I think this means for administrator to be able to specify what fields are required. Not just for Sage to show * next to officially-required fields.
The new 2014 version 'required fields' flag is NOT what this idea is requesting. it appears to be fixed. This idea is requesting a client specified set of fields.
Hi Sage, any feedback re this planned idea?
As discussed, the current asterix on system-required fields is a good start, but that is not what the idea requested -
(My emphasis) : "THE ADMIN to be able to set a "required" flag on fields in the UI to ENFORCE data entry"
This note to Sage posted 25 May 2015. Original idea posted - who knows when (the Idea forum doesn't appear to value dates much)
Restarted this idea as 26945, because Sage marked this as planned but then just stuck an asterisk on system-required fields, instead of enable the system ADMIN to decide which fields to make compulsory. SJC, 31/May/2016
Hi Sage, if you think this is completed, why not designate it completed? Posted 22 January 2020
Many companies/customers require you to have their PO on the Invoice. Having a "required" PO field, in the OE area, and in customer setup will guarantee sales people HAVE to enter a PO# on particular customers. This will eliminated the constant rejection of invoices not being paid due to lack of information. I'm sure this feature could be used in other modules as well.
It seems all their efforts are in CRM these days....
Definitely a good option to have and, a small info hover over that can be populated with what the value should. A given field with Sage's descriptor may actually be used to input a value that is not necessarily say "PO Number".
Comments
Absolutely. All too often important info such as customer/vendor address, contact details etc etc are omitted by users.
Second that!
I completely agree
A "must have". It will prevent orders being shipped without ship-to addresses.
I agree as well. We have to customize this into the UI. Not the kind of customizations I want to see.
ability to attach validation rules would be a plus
Completely agree. Needed for data entry - e.g. the Tax group field in AP miscellaneous payments when you don't select a vendor.
"required" flag on fields in the UI to enforce data entry -- is a MUST
I think this means for administrator to be able to specify what fields are required. Not just for Sage to show * next to officially-required fields.
The new 2014 version 'required fields' flag is NOT what this idea is requesting. it appears to be fixed. This idea is requesting a client specified set of fields.
Hi Sage, any feedback re this planned idea?
As discussed, the current asterix on system-required fields is a good start, but that is not what the idea requested -
(My emphasis) :
"THE ADMIN to be able to set a "required" flag on fields in the UI to ENFORCE data entry"
This note to Sage posted 25 May 2015.
Original idea posted - who knows when (the Idea forum doesn't appear to value dates much)
Restarted this idea as 26945, because Sage marked this as planned but then just stuck an asterisk on system-required fields, instead of enable the system ADMIN to decide which fields to make compulsory. SJC, 31/May/2016
Hi Sage, if you think this is completed, why not designate it completed?
Posted 22 January 2020
Many companies/customers require you to have their PO on the Invoice. Having a "required" PO field, in the OE area, and in customer setup will guarantee sales people HAVE to enter a PO# on particular customers. This will eliminated the constant rejection of invoices not being paid due to lack of information.
I'm sure this feature could be used in other modules as well.
It seems all their efforts are in CRM these days....
Definitely a good option to have and, a small info hover over that can be populated with what the value should. A given field with Sage's descriptor may actually be used to input a value that is not necessarily say "PO Number".