Stream: troubleshooting

Topic: setting a field to 'hidden' does not work?

Laura Huis in 't Veld (Nov 17 2025 at 14:18):

Dear Dataverse users,
We are in the process of upgrading to version 6.7.1.
While testing, I noticed that if I set a field (in this case from the citation block) to hidden, this does not apply. Am I missing a new setting/configuration, or is this a bug?
These are the steps I followed:

1. Create a new dataverse
2. Set the fields 'Series' and 'related material' to hidden by unchecking the checkboxes.
3. Click done.
4. Click 'save changes'.
5. Add a dataset. I expected these fields not to be visible when creating a new one, but I still see them.

Best wishes,
Laura

Philip Durbin 🚀 (Nov 17 2025 at 14:21):

Hmm, I'm not aware of this bug. @Laura Huis in 't Veld can you reproduce this on https://demo.dataverse.org ?

Laura Huis in 't Veld (Nov 18 2025 at 09:27):

Yes, I just tried. After selecting fields to be hidden and saving the dataverse, you will still see the fields when creating a dataset. If I open the General Info page again, my settings haven't been saved.

Philip Durbin 🚀 (Nov 18 2025 at 12:04):

Can you please open an issue?

Laura Huis in 't Veld (Nov 20 2025 at 14:18):

I just created https://github.com/IQSS/dataverse/issues/11992.

My colleagues have been busy figuring out where this went wrong, and also created a fix.
(We still need to test it.)
They concluded that in version 6.6, with the changes for 'display on create' on collection level, some code that checks if a field should be included or not was left out.

Laura Huis in 't Veld (Nov 20 2025 at 14:20):

They also found another omission that had to do with the dataversefieldtypeinputlevel table.
To technical for me to explain, but I guess if we are ready a PR can be done.

Philip Durbin 🚀 (Nov 20 2025 at 14:52):

@Laura Huis in 't Veld thanks so much for creating the issue! I'm looking forward to looking at the PR!

Last updated: Jan 09 2026 at 14:18 UTC