Forum Discussion
What is the plan for "modern" Document Sets?
- Its too early to put specifics on the roadmap - but we will update document sets. We are not being "classic Microsoft" here - there is a steady stream of requests for docsets (along with other parts of classic ECM) and I've never pretended otherwise. Fear is not part of the plan. I hope to be able to give roadmap updates at SPC or Ignite this year, if that helps.
Whereas I find that when suddenly presented with a bar full of buttons that appeared on no other screen (most of which don't do anything very useful but can cause serious problems) people press them esepcailly wgen they options they use in every other library are gone.
After nearly 35 years as an IT trainer, I still think that inconsistent UI and unpredictable behaviour is one of the things that makes technology a disappointment to most people - they like to feel they understand something and then when they find they don't it's like being slapped in the face by a friend .c.f the confusion that is teams vs groups vs UI in outlook vs ui in mail, browse library vs files, e-mails to a group address not being visible in the corresponding teams UI, planner appearing and disappearing depending on where you click etc .etc
Today I was helping user who had put a date column as a document property in word - when she viewed the same document in word online the date switched to one day earlier - no idea why but how could this happen?
Julie Sanders wrote:I feel that changes over the past few months for Doc Sets have been a great improvement - much more consistent with modern UI. I have just finished a handful of webcasts for a client and unfortunately have to explain the differerent UI for things like tasks, doc sets, etc., but they don't seem to really notice - SharePoint is new to them so that's just the way it is.
Out of interest, is your timezone BST? I've seen issues when doing SharePoint development where I've entered a date as, for example, 16/08/2017. This gets stored within the list as 16/08/2017 00:00:00 which is fine for BST. However the underlying timezone is UTC, which means that the date saved is actually 15/08/2017 23:00:00, which is probably why you're getting a discrepancy between the two applications. What the solution is in O365, I unfortunately don't know (yet), other than reverting your site settings to UTC.