@nhontran we couldn't reproduce it. is it possible to share a repro project with us send the link to info@abp.io with the question number.
now you have enough credits :)
is your ABP CLI and Suite 4.0.2?
https://community.abp.io/articles/how-to-customize-the-login-page-of-an-abp-blazor-application-by4o9yms
1- I want to have a navigation property that is mandatory but I don't see any option on abp suite to specify it.
This is not supported for now but it's on the roadmap (probably in v4.2). for now you can do it manually.
In the same subject if I add manually a navigation object property (Shopfloor) in addition of my navigation id property (ShopfloorId) on my entity when I make an update on abp suite this navigation object is deleted.
Suite overwrite all its own created files. So when you edit a Suite generated file, it will be overwritten if you generate the same entity.
actually the problem is related to using module source-code inside the main application and creating CRUD pages with your hybrid structure. A module consists of several database providers and UI frameworks. Therefore Suite is trying to generate code for each of them. What's the official way of doing this; create your CRUD pages inside your module solution. If you reference entities between your modules, you are breaking all best practises because after that you strictly depend on your module.
as I learnt from the Angular team, this is in the milestone and you can achieve this with v4.2-preview. Current version 4.1-preview.
can you try with the 4.1.0-rc.2
dotnet tool install --global Volo.Abp.Cli --version 4.1.0-rc.2 && abp suite update