The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I'm reusing the same field for all my content types and save lineage is enabled. I've added data and I understand that once data is there, the option to toggle save lineage on/off cannot be changed. However, I didn't expect save lineage to be disabled for new content types. I thought it would be disabled in the "on" setting because the existing field had it turned on. Am I missing something? Does this mean I have to always create a new fields if I want to save lineage for new content types?
| Comment | File | Size | Author |
|---|
Comments
Comment #2
br0kenYou understood it correctly, @chrisck however I see that the message is lacking this information so it's good to have it added.
The `Save lineage` option works only with the `Cardinality` set to `Unlimited`. The `Cardinality` cannot be changed if the field storage has at least one entry, imposing the same restriction to `Save lineage`. The field storage layout (typically a database table) is designed to store values for the entire entity type, making the field storage reusable across its bundles.
@chrisck, in your case you have to use two fields - one with `Save lineage` enabled and another - disabled and reuse them accordingly across multiple content types.
Comment #3
br0kenOh, jeez, I misunderstood the problem, sorry. You are right @chrisck, there is the problem with not persisting the "on" state of the `Save lineage` option if the field is reused.
Comment #4
chrisckThanks for confirming this is a bug. Yes cardinality didn’t change, it is set to unlimited. “Save lineage” was previously enabled when the table was empty.
I wanted to reuse the same field with “save lineage” on for a new bundle but was unable to due to existing data. Cardinality for the field is still set to unlimited.
Interestingly I’ve tried clearing all data in the tables but cannot enable “save lineage” for new bundles. It’s as if Drupal locks this setting as soon as there is data, regardless if the data is deleted. The only way at the moment is to delete the field and recreate it on all bundles before entering data.
Comment #7
br0kenPlease try the latest
3.x-devor2.x-devand let me know if the problem still persist.Comment #8
chrisckTested 2.x-dev and can confirm the issue is fixed. The "save lineage" is now showing "on" but the checkbox is disabled as expected when reusing an existing field with a new bundle. Thank you so much for the quick fix :)