Hi,
We have deployed the diagnostic services and collected the logs. Please find the detailed diagnostic output attached in the email.
Thanks
Hello i have created another query please reply in that
No you did not understand what i am asking
i have check this query also in administation host and tenant databse
SELECT * FROM AbpFeatureValues WHERE Name LIKE '%TourModule%' OR Name LIKE '%TourService%' ORDER BY ProviderName, ProviderKey;
no record
Screenshot of the Feature Management UI with TourModule disabled — and please note whether you're viewing it as Host or as a specific Tenant
see feature only able to see in host under saas of tenants tabs, okay?
and permission I am seeing under tenant login and roles section
The feature values from the database:
no record in tenant
Which ABP version you're using for this environment
ABP Commercial v9.2.0 with .NET 9.0
We checked our TourService backend. All permissions already have .RequireFeatures() configured:
TMSMSFeature.cs:
public const string GroupName = "TourModule"; public const string Tour = GroupName + ".TourService"; // = "TourModule.TourService"
FeatureProvider.cs:
myGroup. AddFeature(TMSMSFeature.Tour, defaultValue: "false", ...);
TourServicePermissionDefinitionProvider.cs:
Every permission already has .RequireFeatures(TMSMSFeature.Tour)—for example:
myGroup.AddPermission(TourServicePermissions.TourCategories.Default, ...) .RequireFeatures(TMSMSFeature.Tour); tourCategoryPermission.AddChild(TourServicePermissions.TourCategories.Create, ...) .RequireFeatures(TMSMSFeature.Tour);
All permissions in the file follow this pattern. So the issue is not missing .RequireFeatures() — it's already there on every permission. Despite disabling the feature in the Feature Management UI, permissions still appear. Could this be a framework-level issue with permission UI not respecting RequireFeatures when listing?
one more thing. Suppose I have 20 microservices module wise in that in one production I just use only 1 module and with your ABP, all common microservices so when i make new production environment, ABP makes my default admin role with all permissions. then in this we have features like this or not that, whatever feature is assigned as module to that production that only permission goes in admin and fetch also that only
OKay Thank you so much. i will deploy this in all my production environments and test it and if there are any further issues, I will let you know
So now do I need to remove all logs and this final optimized code update in all three of my productions?