Fall back to a valid default view when switching between objects with different layouts

Users want the system to automatically show a valid default view when navigating to an object whose layout does not include the previously active tab, instead of throwing an error that interrupts the workflow. Problem / Pain: When a user switches between objects that have different layouts, the system tries to restore the previously active tab. If that tab does not exist in the new object's layout, the system throws an error instead of gracefully switching to a valid view. From the user's perspective this is confusing and disruptive. They simply navigated to a different object and are now faced with an error they cannot explain or easily recover from without reloading the page or navigating away. Impact / Benefit: Automatically falling back to the default view of the new object whenever the previously active tab is not available would eliminate a confusing and unnecessary error state. Users could switch between objects freely without risk of hitting a dead end, making navigation more reliable and the system more stable in everyday use. Example use case: A PIM manager is working in the detail view of a product record with the specifications tab open. They navigate to a different product that has a simpler layout without a specifications tab. Instead of seeing a valid view of the new product, they receive an error. With automatic fallback, the system would simply open the default tab of the new product and the manager could continue working without interruption. Idea source: Customer Feedback Voting note: Vote for this idea if this need is relevant to you as well.