I did contact support regarding this issue of the dates not syncing and I just got it resolved yesterday after a lot of trial and error. I want to share the solution or reason for the unexpected behavior.
To recap what the issue is .... I have different modules in the same model, using the same Calendar and Time Scale and not filtered showing different time selections.
First of all, I had to convince a lot of people I talked to - including some in support- that the expected behavior is for the date (and every other dimension) in a model to sync. That alarmed me because this is a basic concept.
When one first creates a module, Time is placed on Columns. I prefer to have time as a page selector - at least while developing-. So when I forgot to move the Time dimension to Pages while creating the module, I would pivot the module and save the view with the time in pages as the default view.
These modules with an "overridden" default view were the ones not syncing. Apparently, when you override the default view with time in Pages - set on Feb 20 for example -, every subsequent time you open the module it will have Feb 20 regardless of the time currently selected in the rest of the model. I don't know if that's the intended behavior or what is the logic /benefits behind it, but I find it confusing.
If instead of saving the view as a default view -after you move time to the pages section- you save it as another view, the time dimension will sync in the new saved view with the model without an issue.
This is not a Time only issue, the behavior is the same when any other dimension in the model
This might not be a common issue that many people face or are irritated by it, but I have a knack of finding rare exceptions (it's a curse 🙂) and I don't settle until I find the underlying reason.
Hope that was helpful
Einas "Give a Man a Fish, and You Feed Him for a Day. Teach a Man To Fish, and You Feed Him for a Lifetime"