<lpx-sidebar> <profile-widget class="floating-widget"> </profile-widget> </lpx-sidebar>
and have custom method to backToImpersonator() how can i go back to impersonator
I am using the above code to display login user info and impersonation option to the left side. i am able to see the back button but when i click on that nothing is happening
We have relocated the logout option to the bottom of the left side menu in our Angular application and hidden the right sidebar. After making these changes, we are no longer able to revert to the original user after impersonation.
okay Thank you
Currently we hold team plan + two additional developer license in ABP . we could like to downgrade our license to team plan + one developer seat . can you pls change existing license . so that we can proceed with the payment .
I have installed the Volo.Abp.Http.Client.IdentityModel package in the Host module of Service A and configured it in HttpApi.HostModule.cs as outlined in the documentation.
Please share your code and appsettings configuration
Please confirm if the appsettings below look correct, and I will proceed to share the code. appsettings.json (Service A)
"RemoteServices": {
"Default": {
"BaseUrl": "https://localhost:44325"
},
"ServiceB": {
"BaseUrl": "https://localhost:44371/",
"UseCurrentAccessToken": true
}
},
"IdentityClients": {
"Default": {
"GrantType": "client_credentials",
"ClientId": "AdministrationService",
"ClientSecret": "1q2w3e*",
"Authority": "https://localhost:44322",
"Scope": "Service B"
}
},
Here is a similar question, can you share your code
https://abp.io/support/questions/2803/VoloAbpHttpClientAbpRemoteCallException-Unsupported-Media-Type
After modifying it at the controller level, it worked. However, I am still unable to access CurrentUser in Service B. Additionally, the Service B method is only triggered when I annotate the API method with AllowAnonymous. I have installed the Volo.Abp.Http.Client.IdentityModel package in the Host module of Service A and configured it in HttpApi.HostModule.cs as outlined in the documentation.
Service B from the Service A. Following the documentation for Synchronous Interservice Communication, I implemented the integration. However, when attempting to call the API, I encountered the following exceptionVolo.Abp.Http.Client.AbpRemoteCallException: 'Unsupported Media Type'
you can check this document to know how to add a custom filter.
https://abp.io/docs/latest/framework/infrastructure/data-filtering
I have already gone through the documentation when i try to keep the below code in dbcontext getting no suitable method to overload error on CreateFilterExpression method
protected bool IsBranchFilterEnabled => DataFilter?.IsEnabled<IBranchEntity>() ?? false;
protected int? CurrentBranchId => BranchContext?.CurrentBranchId;
protected override bool ShouldFilterEntity<TEntity>(IMutableEntityType entityType)
{
if (typeof(IBranchEntity).IsAssignableFrom(typeof(TEntity)))
{
return true; // Apply filter to all entities implementing IBranchEntity
}
return base.ShouldFilterEntity<TEntity>(entityType);
}
protected override Expression<Func<TEntity, bool>> CreateFilterExpression<TEntity>(ModelBuilder modelBuilder)
{
var expression = base.CreateFilterExpression<TEntity>(modelBuilder);
if (typeof(IBranchEntity).IsAssignableFrom(typeof(TEntity)))
{
// Build the filter for BranchId
Expression<Func<TEntity, bool>> branchFilter = e =>
!IsBranchFilterEnabled ||
(EF.Property<int?>(e, "BranchId") == CurrentBranchId || EF.Property<int?>(e, "BranchId") == null);
// Combine the new filter with existing filters
expression = expression == null ? branchFilter : QueryFilterExpressionHelper.CombineExpressions(expression, branchFilter);
}
return expression;
}
I need to create a custom filter to filter my entity based on BranchId. The BranchId will be received as a List<long> from the request headers or parameters. Here's the approach I followed:
Created IBranchEntity Interface:
Domain.Shared folder.BranchId property, which I inherited in the relevant entity.Defined IBranchContext Interface:
CurrentBranchId property to store the branch ID.BranchContext class in the Http.Host project with the necessary logic.
Entity Framework Filtering Logic:
EntityFramework folder to define filtering logic for entities.
Service Registration:
IBranchContext in the HostModule.cs under the ConfigureServices method as follows:
context.Services.AddHttpContextAccessor();
context.Services.AddScoped<IBranchContext, BranchContext>();
Database Context Changes:
ClinicServiceDbContext constructor to accept the IBranchContext.
private readonly IBranchContext _branchContext;
public ClinicServiceDbContext(
DbContextOptions<ClinicServiceDbContext> options,
IBranchContext branchContext
) : base(options)
{
_branchContext = branchContext;
}
protected override void OnModelCreating(ModelBuilder builder)
{
base.OnModelCreating(builder);
builder.ConfigureClinicService();
builder.ConfigureBranchFilterForEntities(_branchContext);
}
After implementing the above, the filter is correctly identifying entities with the BranchFilter when the application is initially loaded. However, it is not being triggered for subsequent requests.
