Blueprint syncs should not override set dates with nulls
Our delivery model leverages Blueprints that are associated with courses that have varying start/end/ module lock dates. Our courses are technical Bootcamps about 6 months in length, and they do not follow a traditional Semester system.
We set the module unlock dates for each class, but then when we need a blueprint sync to correct a content issue or add something new, those dates are overwritten with nulls because there are no dates on the blueprints themselves.
This leads to lots of manual work and problems for us, of course, but it's also much better design to leave data in place rather than removing it on any sort of sync. If a value is set in a child, a value NOT set in the parent should not remove it.
Thank for your consideration!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.