Bulk Meta Data Edit Resetting Custom Field

[toomuchreading]

First things first. The version of Calibre I'm using is 7.24.

I added a custom field to calibre. Went fine. Just a read column with yes/no selection. I had most of my books set with the proper read/not read check marks. So far so good.
I then today I decided to update the tags in my database using the bulk edit meta data function. Every single tag got reset back to X, if I had a check mark there.
How can I prevent Calibre from resetting the field when I do a bulk edit, when I want it to stay the way it is? When I want to change the field in bulk, it works great.

[chaley]

I can't repeat your problem, at least as I understand it.

Steps I took:
1) create a custom yes/no column called #mybool
2) put 'Yes' in some books (green check)
3) put 'No' in some books (red X)
4) leave some books as undefined (empty)
5) select the above books.
6) run bulk edit. I do not touch the box for #mybool, leaving it as 'undefined'
7) change some other metadata fields (I tried several)
8) Press OK

The booleans remain as they were. No changes.

What are you doing different from the above?

[Manichean]

You're sure you didn't accidentally change the value of the field in your bulk edit?

[toomuchreading]

Originally Posted by chaley

I can't repeat your problem, at least as I understand it.

Steps I took:
1) create a custom yes/no column called #mybool
2) put 'Yes' in some books (green check)
3) put 'No' in some books (red X)
4) leave some books as undefined (empty)

What are you doing different from the above?

I don't have undefined available to me. I just have the green check and the red x available.

It looks like, even though I don't go the custom field tab, everything no matter what, unless I change it to green check is set to red check.

[speakingtohe]

iI seem to remember reading that there was a way to change the default value for Y/N fields. Could this have inadvertantly happened?

[theducks]

Originally Posted by speakingtohe

iI seem to remember reading that there was a way to change the default value for Y/N fields. Could this have inadvertantly happened?

There is a "Tweak" to set Y/N(Boolean) to Tri-state.
If something happened to the Tweak file, it resorts to default.
I would guess, that if you copied the library to another system, the tweaks had better be the same .. Before.

[chaley]

Originally Posted by toomuchreading

I don't have undefined available to me. I just have the green check and the red x available.

It looks like, even though I don't go the custom field tab, everything no matter what, unless I change it to green check is set to red check.

The only way that can happen is if you changed the tweak

bool_custom_columns_are_tristate = 'yes'

to be

bool_custom_columns_are_tristate = 'no'

I confirm that the bug exists when the tweak is set to no. I will look at fixing it. In the meantime, the workaround is to change the tweak back to 'yes', but that will have the side effect of permitting boolean columns to be Yes/No/empty instead of just Yes/No.

[chaley]

A fix has been submitted for release.

This code has been broken since May. Shows how often that tweak is used.

[toomuchreading]

Originally Posted by chaley

A fix has been submitted for release.

This code has been broken since May. Shows how often that tweak is used.

All's it takes is just one user to find out where something 'went wrong' and the correct people to figure it out with the correct clues! I totally forgot about setting that tweak.

Absolutely fabulous work investigating and getting a fix in place! I look forward to giving it a try again.