When navigating from a record in the new layout to a related contact (in a different app/workspace) and then returning to the original record via the related link, the record opens in the old layout instead of the new default layout. This occurs despite the app being fully converted and set to use the new record layout for all users. The issue suggests that navigation through related items does not preserve or respect the enforced default record type.https://www.loom.com/share/ab624ee22dcc42e58eec7bf387daab20
2 Likes
Hi @ViweSiveXozwa,
thank you very much for the report, and also for the video, this is really helpful.
I’ve checked it, and it clearly shows which link type leads to the old record experience being used. This helps us pinpoint exactly where the issue is.
We will fix this and let you know as soon as the fix is live.
Thanks again for your help, and have a nice day!
Leo
1 Like
@ViweSiveXozwa we appreciate the report and patience. 
The team pushed a fix today - could you verify on your end that this is now working as expected (a page refresh will be required)?
Thank you in advance,
Cheers &
Happy weekend 
3 Likes
It is working. Thanks
2 Likes
@Tim and @Leo - I have a scenario where this same bug is appearing again, but in the opposite direction.
App A is a legacy Tasks app, not yet converted to the new record layout (planning a release for that soon as it’s a huge improvement, but that’s beside the point)
If any user goes to App A directly, it opens with the view they expect in the old record type.
App B is a newer app that is using the new record layout.
App B has a relationship field to App A allowing users to log new tasks. However when using that option, it opens App A in a view of the new record layout, which looks terrible (almost unusable) as it has not yet been designed and converted to that new layout.
This issue makes it very hard to test, and unusable to add the needed feature in App B until App A becomes converted.
Is this expected behavior?
1 Like