Updated: Comment #0
Problem/Motivation
Currently in Drupal 7, field cardinality is determined per field definition. This means that if I have an unlimited-cardinality field on one content type, all other content types that use that field also have to be unlimited cardinality. This means that if you have multiple content types with different cardinality needs, you will need to create multiple fields in order to handle this.
This is bad, because it means adding multiple views, complicating rules and reports, and making things more difficult in general.
Proposed resolution
Field cardinality settings would need to be determined from the instance configuration, not the field definition configuration.
Remaining tasks
User interface changes
The cardinality setting would need to be moved from the field settings tab to the field instance edit tab.
Comments
Comment #7
dpiDuplicate of #1029298: Allow cardinality to be restricted (overriden and reduced) in the field instance settings