Yes, I agree. I asked the same thing several weeks ago. I can generate the name in my helpers, but for many of them (rating, etc.) it would be helpfull not to require name. ID is unique and should be enough, I guess… Or is there any other problem why name is required (for example rewrite rules for URL, etc.)?
How do you generate the name using helpers? I haven’t tried using them yet.
I understand that something has to be required but I have a pod type that doesn’t really have a need for a name and it’s gonna be really tedious to have to add one every time that’s meaningful.
Wouldn’t it make more sense to have all pods have an ID field that is required? I know most of the time it makes more sense to list pods by their name, but when that’s not the case it makes pods sort of difficult to work with.
My specific example is a system for tracking donations. So my "donation" pod has fields for Donor (picked from a list of "donor" pods), Amount and Date. I can’t really think of a good way to name them other than repeating another field (like the donor or date).
We’re working on a fix in the near future to not require a name field. This was included by default because it’s used for Search, for generating Permalinks, and in the UI of the Pod item management screens.
I realized that if I don´t show the name field on my management screen, I don´t have the
Edit | Duplicate | Delete links… is that a way to tranfer this to another field?
It would be awesome if we could decide which field to be the "main" field in a pod.
You must be logged in to reply to this topic.