Nic E. - 2 years ago
Woah, so 8 years and no response. Does salesforce monitor these ideas, because I have never actually seen progress on one. I've seen some marked as delivered, but not actually delivered, and a whole lot just ignored. How hard is it to just allow the removal of the name field from the page layout, because that (with triggers) would fulfill the need.
Syeda Fatima - 4 years ago
both things are important.
For most of the standard object records, we do not have auto number field as its name. User should be allowed to leave Name of record while inserting a new one and Name should be auto-populated with the help of an auto number and some prefix (which is not available in Auto number display format for example some field value).
Amanda Summers - 5 years ago
Both of the options you mention are good, but I'd vote for allowing default values to be set for standard fields. Like Dennis said, we can create a new NEW button to get the default to display. However, the original idea is still my ultimate preference.
Just so you know where I'm coming from, at this time I've run out of fields in a very heavily used object (Projects) and have decided to create a custom object to relate to it that will take over most of the field burden (finance calculations). Right now there are over 7,000 project records and as we move forward with creating these related (1to1) records I'd love for them to have the same identifying number to reduce confusion. ie PR-111056 = PF-111056
Both of your options are helpful, but both also allow my users to edit the value and no matter how much I watch them, it's going to happen by accident. The project finance records will be reviewed by our CFO, CEO, COO, etc and they have to be reliable. That's why I just voted for this idea. :)
Brett Moan - 5 years ago
Why is there no status on this?
This is a simple feature, and has had requests fro over 7 years.
Not allowin the creation of NEW items with a systematic value for "Name" without first giving a dummy value for the field is stupid. It would be simple enough to change the validation of the required fields to first run all workflow rules of "on create or edit" .
Please respond with status on this feature.
Kyle McKay - 6 years ago
There are a couple of enhancements regarding default values that are currently higher on the backlog for my team that I think would address a large part of this, which are:
When can we expect these features?