Hello,
When RequireFeatures is added to permissions;
Host admin does not see the Management Service menu at all
Management Service pages where the customer is included in the package and visible
Is there a way for the Host admin to view the Management Service section in this scenario?
When we tried our checks with StateCheckers instead of RequireFeatures;

The code structure below appears to be for Categories, but it is managed with the same coding in the CategoryType structure, but the naming is different.

When we log in with Host Admin, we see two pages and can view data.

However, when we log in with a tenant;

You can access the Category page included in the package without any problems, but when you click on it, the CategoryType page appears even though there is no CategoryType in the package assigned to the tenant.
The page is visible, but we do not want this page, which is not included in the package, to appear in the menu at all.
In this scenario, it needs to be configured so that the Tenant cannot see pages that are not included in the package. Is there a way to do this?
AbpSuiteVersion: ABP Suite v9.3.5
Hello, when we create an unrelation table in a sample microservice project, we do not have any problems, but when we want to add a relation table, using importContryProj.ManagementService.Shared; is added in our CountryControllerBase class, but since we have nothing related to shared, using also gives an error. Below, I am sharing the steps for creating an example. We kindly request your support
Hello
We are creating a new microservice project, then running it to ensure it works. Next, we add the ManagementService microservice to our project and build it to ensure it works. We then run our project to ensure it runs without errors. After that, we create the Products table in ManagementService via AbpSuite.
Here, we see that the Generating proxies section shows 0 ms. After checking, we see that files like entity appService have been created on the ManagementService backend side, but when we check the projects folder in Angular, we only see the abp -solution1 folder created during the project's initial stage. We did not see any folder or file related to management-service. Similarly, we did not see any files related to the products table we added via AbpSuite. Consequently, we have no access to any products table in the panel! I would like to mention that we also followed the steps in the readme files provided after creating the project, such as generate-proxy.
We did not encounter this issue in our samples a few updates ago. Could you please advise us on the areas we should check?
Thanks.
Hello again. I've checked new updates but I've taken different error from angular. I press login button and then I saw this page. Please review this error.
Thanks.
Hello, today I created a new project, but I got an error again. Please review this problem and fix the errors in this version. Best regards.
Hello, our tenant will be obtained from an external form for our project. When the tenant is included in the system, a default edition assignment will be made, and we will want to control the permission statuses of this tenant. In the current scenario, we are conducting our tests by adding a tenant through the admin panel without using an external form and assigning the edition we created to this tenant.
Regarding the problem we are experiencing;
When a tenant is added to the system, role assignments are made by default. When there is no distinction in permissions for these role assignments (MultiTenancySide or RequiredFeature), all permissions are assigned to this role. However, we only want to assign permissions that contain features valid for editions assigned to the tenant to that tenant. For this reason, we use the RequiredFeature property, which you mentioned is available for permissions, to establish the connection between permissions and features. However, in this case, we encounter the following situation. We assign the edition we created with the desired features to the tenant. Afterwards, when we log into the system with the tenant assigned to the edition, we cannot access the menus included in the edition. Upon checking, we see that no record has been added to the PermissionGrant table. However, we noticed that if, for example, the Category permission exists and the project runs without adding the RequiredFeature tag to the permission beforehand, the Category permission is recorded in the PermissionGrant table for the tenant. Afterwards, when we add the RequiredFeature tag to the Category permission, we see that it works. After adding the RequiredFeature tag, we see that it works. However, when a new tenant arrives after this process, the RequiredFeature tag is present, so no record is added to the PermissionGrant table again. In short, what we want here is to be able to control the tenant's permission status on a feature-specific basis.
we kindly request your support.
thanks
Hello,
The project features I created are as described above. When I create an entity in ABP Suite, I encounter the error shown in the screenshot I attached.
I would appreciate it if you could provide a solution to this error.
Best regards.
Hello, I have a customer, my customer has customers, I want to limit the customers and users that my customer will create here, is there a place where I can do this from your interface or do you have an infrastructure for this. Good work