Activities of "yazilim.ithinka"

Question
  • Template: microservice
  • Created ABP Studio Version: 1.3.3
  • Current ABP Studio Version: 1.4.2
  • Multi-Tenancy: Yes
  • UI Framework: angular
  • Theme: leptonx
  • Theme Style: system
  • Theme Menu Placement: side
  • Run Install Libs: Yes
  • Database Provider: ef
  • Database Management System: postgresql
  • Mobile Framework: react-native
  • Public Website: Yes
  • Social Login: Yes
  • Include Tests: Yes
  • Dynamic Localization: Yes
  • Kubernetes Configuration: Yes
  • Grafana Dashboard: Yes
  • Use Local References: No
  • Aspire: Yes
  • Optional Modules:
    • GDPR
    • FileManagement
    • TextTemplateManagement
    • AuditLogging
    • OpenIddictAdmin
  • Selected Languages: English, Turkish
  • Default Language: English
  • Create Command: abp new CarbonAI -t microservice --ui-framework angular --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --aspire --dont-run-bundling -no-language-management -file-management

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

  • A package was created.
  • Category and CategoryType properties were added to the package.
  • A tenant was created.
  • A package was assigned to the tenant.
  • A tenant logged in. The menus assigned to the package were displayed in the Management Service menu.
  • A tenant was logged out.
  • A host admin was logged in.
  • A Management Service was not visible in the menu.

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.

  • A package was created.
  • A category was added to the package.
  • A tenant was created.
  • A package was assigned to the tenant.
  • A tenant was logged in. All pages included and excluded from the package were visible. However, clicking on a page not included in the package resulted in a 403 permission-free page. The tenant should not have been able to view pages outside of the package. Note: Here, we saw that when the permissions related to the tenant's CategoryType were manually removed from the PermissionGrant table, the tenant was unable to view the page.
  • A tenant was logged out.
  • A host admin was logged in.
  • All pages under the Management Service were visible, and access was unproblematic.

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?

Question
  • Template: microservice
  • Created ABP Studio Version: 1.3.3
  • Current ABP Studio Version: 1.3.3
  • Multi-Tenancy: Yes
  • UI Framework: angular
  • Theme: leptonx
  • Theme Style: system
  • Theme Menu Placement: side
  • Run Install Libs: Yes
  • Database Provider: ef
  • Database Management System: postgresql
  • Mobile Framework: react-native
  • Public Website: Yes
  • Social Login: Yes
  • Include Tests: Yes
  • Dynamic Localization: Yes
  • Kubernetes Configuration: Yes
  • Grafana Dashboard: Yes
  • Use Local References: No
  • Aspire: No
  • Optional Modules:
    • GDPR
    • FileManagement
    • TextTemplateManagement
    • AuditLogging
    • OpenIddictAdmin
  • Selected Languages: English, Turkish
  • Default Language: English
  • Create Command: abp new importContryProj -t microservice --ui-framework angular --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-language-management -file-management

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

Question
  • Template: microservice
  • Created ABP Studio Version: 1.3.2
  • Current ABP Studio Version: 1.3.2
  • Multi-Tenancy: Yes
  • UI Framework: angular
  • Theme: leptonx
  • Theme Style: system
  • Theme Menu Placement: side
  • Run Install Libs: Yes
  • Database Provider: ef
  • Database Management System: postgresql
  • Mobile Framework: react-native
  • Public Website: Yes
  • Social Login: Yes
  • Include Tests: Yes
  • Dynamic Localization: Yes
  • Kubernetes Configuration: Yes
  • Grafana Dashboard: Yes
  • Use Local References: No
  • Aspire: No
  • Optional Modules:
    • GDPR
    • FileManagement
    • TextTemplateManagement
    • AuditLogging
    • OpenIddictAdmin
  • Selected Languages: English, Turkish
  • Default Language: English
  • Create Command: abp new AbpSolution1 -t microservice --ui-framework angular --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-language-management -file-management

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.

  • Template: microservice
  • Created ABP Studio Version: 1.3.2
  • Current ABP Studio Version: 1.3.2
  • Multi-Tenancy: Yes
  • UI Framework: angular
  • Theme: leptonx
  • Theme Style: system
  • Theme Menu Placement: side
  • Run Install Libs: Yes
  • Database Provider: ef
  • Database Management System: postgresql
  • Mobile Framework: none
  • Public Website: Yes
  • Social Login: Yes
  • Include Tests: Yes
  • Dynamic Localization: Yes
  • Kubernetes Configuration: Yes
  • Grafana Dashboard: Yes
  • Use Local References: No
  • Aspire: No
  • Optional Modules:
    • GDPR
    • TextTemplateManagement
    • AuditLogging
    • OpenIddictAdmin
  • Selected Languages: English, Turkish
  • Default Language: English
  • Create Command: abp new AbpSolution3 -t microservice --ui-framework angular --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-file-management -no-language-management

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.

  • Template: microservice
  • Created ABP Studio Version: 1.3.0
  • Current ABP Studio Version: 1.3.0
  • Multi-Tenancy: Yes
  • UI Framework: angular
  • Theme: leptonx
  • Theme Style: system
  • Theme Menu Placement: side
  • Run Install Libs: Yes
  • Database Provider: ef
  • Database Management System: postgresql
  • Mobile Framework: none
  • Public Website: Yes
  • Social Login: Yes
  • Include Tests: Yes
  • Dynamic Localization: Yes
  • Kubernetes Configuration: Yes
  • Grafana Dashboard: Yes
  • Use Local References: No
  • Aspire: No
  • Optional Modules:
    • GDPR
    • TextTemplateManagement
    • AuditLogging
    • OpenIddictAdmin
  • Selected Languages: English, Turkish
  • Default Language: English
  • Create Command: abp new AbpSolution2 -t microservice --ui-framework angular --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-file-management -no-language-management

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.

  • Template: microservice
  • Created ABP Studio Version: 1.1.2
  • Current ABP Studio Version: 1.2.2
  • Multi-Tenancy: Yes
  • UI Framework: angular
  • Theme: leptonx
  • Theme Style: system
  • Theme Menu Placement: side
  • Run Install Libs: Yes
  • Database Provider: ef
  • Database Management System: postgresql
  • Mobile Framework: react-native
  • Public Website: Yes
  • Social Login: Yes
  • Include Tests: Yes
  • Dynamic Localization: Yes
  • Kubernetes Configuration: Yes
  • Grafana Dashboard: Yes
  • Use Local References: No
  • Optional Modules:
    • GDPR
    • FileManagement
    • TextTemplateManagement
    • AuditLogging
    • OpenIddictAdmin
  • Selected Languages: English, Türkçe
  • Default Language: English
  • Create Command: abp new CarbonAI -t microservice --ui-framework angular --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-language-management -file-management

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.

  • Can we change the tenant's default role assignment status? Can we assign it to a role we created, and can we edit this role status from the interface? In the future, if a permission assigned to a role is removed, it must be removed from all tenants assigned to that role.
  • When we add a RequiredFeature to Permission, is the only way to grant that permission to the tenant to override the method that created the tenant and add permissions one by one by checking the features it contains according to the assigned edition? Is there another way? This method does not seem very sound; problems may arise in the future when packages expand or change. We need to be able to dynamically access the permissions associated with the features within the edition and assign them to the tenant. Of course, when the permission status changes via the panel, the tenant's permission status should change dynamically; permissions should be removed from existing tenants or added to new tenants, and new tenants should directly have the permissions within the existing package content.

we kindly request your support.

thanks

Question
  • Template: microservice
  • Created ABP Studio Version: 1.2.1
  • Current ABP Studio Version: 1.2.1
  • Multi-Tenancy: Yes
  • UI Framework: angular
  • Theme: leptonx
  • Theme Style: system
  • Theme Menu Placement: side
  • Run Install Libs: Yes
  • Database Provider: ef
  • Database Management System: postgresql
  • Mobile Framework: none
  • Public Website: Yes
  • Social Login: Yes
  • Include Tests: Yes
  • Dynamic Localization: Yes
  • Kubernetes Configuration: Yes
  • Grafana Dashboard: Yes
  • Use Local References: No
  • Optional Modules:
    • GDPR
    • TextTemplateManagement
    • AuditLogging
    • OpenIddictAdmin
  • Selected Languages: English, Turkish
  • Default Language: English
  • Create Command: abp new ClassifAI -t microservice --ui-framework angular --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-file-management -no-language-management

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.

Question
  • Template: microservice
  • Created ABP Studio Version: 1.0.2
  • Current ABP Studio Version: 1.0.2
  • Multi-Tenancy: Yes
  • UI Framework: angular
  • Theme: leptonx
  • Theme Style: system
  • Theme Menu Placement: side
  • Run Install Libs: Yes
  • Database Provider: ef
  • Database Management System: postgresql
  • Mobile Framework: react-native
  • Public Website: Yes
  • Social Login: Yes
  • Include Tests: Yes
  • Dynamic Localization: Yes
  • Kubernetes Configuration: Yes
  • Grafana Dashboard: Yes
  • Use Local References: No
  • Optional Modules:
    • GDPR
    • FileManagement
    • TextTemplateManagement
    • AuditLogging
    • OpenIddictAdmin
  • Selected Languages: English, Türkçe
  • Default Language: English
  • Create Command: abp new CarbonAI -t microservice --ui-framework angular --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-language-management -file-management

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

Showing 1 to 8 of 8 entries
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.1.0-preview. Updated on December 17, 2025, 07:08
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.