Hi, same problem too. Do you discover how to fix this? I search and the declaration in the metadata was correct. I try into a custom module, normal module and also expanded and not expanded. The same result always…
I think the problem is in how SuiteCRM (or angular) interprets these parameters, but I don’t know…
Hi, can you plz give specific detail on how to do this?
Never mind, found it:
Classic view route configuration
As mentioned this is configuration driven. Check the configs in config/services/module/module_routing.yaml, the entries that are set to false, will use the classic view (legacy).
Also, any view that is not implemented yet on angular side will default to this classic view.
From an UI perspective you’ll notice some slight differences on the styling/features ( button position, etc)