Did 1-column layouts for Entities suddenly become the default recently? It seems that the first time I view an existing Entity type now, it is defaulting to 1-column layout and it’s awful! Once I change it, it sticks, so that’s good, but this really feels like a terrible choice if what I’m experiencing is happening across the board. And I feel like I must be missing something since I can’t find an existing topic either about this extremely annoying apparent new default, nor an announcement of it having been implemented. I also can’t find a Setting to control it, so I’m left changing it for every entity type I view. Not the end of the world for me personally, I’m more concerned about the collective impact and annoyance it surely must be having on the overall userbase. And to be clear this is happening across two separate Fibery workspaces and accounts, so it can’t just be me… can it? 
The default layout for new entity views was changed in March:
but it should only affect new dbs/entity views.
Existing entity view layouts should not have been affected, so this shouldn’t be happening 
I’m not saying that it’s not happening for anyone else, but you are the first to report this effect 
I presume everyone likes this since you would have received a month of complaints by now if not. But… I effing hate it. Please, please provide a way to change the default!
Well, that’s good I suppose, hah. But yes, it’s happening for me across multiple accounts and browsers (on Windows) and in the app (on Mac). So basically everywhere. Surprising no one else has encountered or noticed it. Do you need anything from me to help track the issue down?
That does sound really weird, and yes we would have expected a load of reports if the issue was widespread (and not liked).
I suspect that if there is a bug that needs fixing for you/your workspace(s) then this is probably independent of any functionality to allow users to choose default layout for new views. IOW I can’t promise that fixing the former will automatically have a side-effect of the delivering the latter.
Just following up on this (sorry for the delay). Here’s the explanation from the devs:
"There is a notion of saved/unsaved layout:
- layout is saved if user has ever changed it (reordered field or changed any unit visualization or changed 1col/2col, etc)
- otherwise it is not saved
In this feature due to tech complexity we went with the following approach:
- saved layout is untouched
- unsaved layout is one col by default
This means any new or unsaved layout(we expected quite a few number of such layouts) will be 1 col by default"
So I presume that what has happened for you is that many (most? all?) of your entity views were ‘unsaved’, meaning that they had not been modified in any way, and were thus migrated to the 1-column layout when the feature was rolled out.
Had any entity view been adjusted in any way (re-ordering fields, hiding them, etc.) then it should be unaffected.
Unfortunately, I’ve not been told of any fix that can be implemented to easily revert the layout change for those entity views where the layout was changed by the feature rollout, sorry.
I see. Well, personally I think Fibery’s 2-column layouts are a big differentiator. 1 column is fine, but really kind of garbage by comparison. 
OK, I’m joking, but seriously is this just an attempt to appeal to the Notion crowd or what? Do you have stats on usage of 1 vs 2 column?
btw: notion started copying fibery’s 2 columns with “layouts”. They added a side panel and pinned fields…