In Gibbon versions prior to v25, the term for a Markbook column was inferred from the date when the column was created.
Later, the explicit “Term” field was introduced, which has been very useful. I typically enable “Group Columns by Term” so columns and totals are grouped correctly by term.
It is very convenient to import columns using DataStructure-markbookColumns.xlsx. In many cases, I fill in the “Term Added” field but leave “Date Added” blank, since it is not required during import.
However, if I later edit one of those imported columns, I cannot save my changes unless I provide a value for “Date”. It is set to the current date by default and can be changed.
Would it make sense to make “Date” non-required whenever “Term” is already filled in?
At that point, the date is no longer needed to infer the term, since the term has already been explicitly defined.
One issue this currently creates is that if a user enters a Date value that conflicts with the selected term, the column can appear under both:
• the explicitly selected term, and
• the term inferred from the date.
Just wondering if this logic could be simplified now that explicit term support exists.
Thanks