Activities of "EngincanV"

Hi, Can you change your UseSwaggerUI middleware as follows?

app.UseSwaggerUI(options => 
{  
    // builds a swagger endpoint for each API version  
    foreach (var description in provider.ApiVersionDescriptions)  
    {  
        options.SwaggerEndpoint($"/swagger/{description.GroupName}/swagger.json", description.GroupName.ToUpperInvariant());  
    }  
    
    var configuration = context.GetConfiguration();
    options.OAuthClientId(configuration["AuthServer:SwaggerClientId"]);
    options.OAuthClientSecret(configuration["AuthServer:SwaggerClientSecret"]);
}); 

Hi @drg_tverkroost, AbpHelper.GUI is not our product, it's an open-source application. Can you create an issue on https://github.com/EasyAbp/AbpHelper.GUI?

knowing that there is 1 million records in this table for each one of the Tenants.

Could your problem be related with this https://stackoverflow.com/a/65440387/10477283?

With version 4.4, EntityFrameworkCore.DbMigrations project has been removed and DbContexts are unified. You can check this community article to understand the circumstances under that. If you were migrated your application from 4.3 to 4.4 please apply the steps in the article to unify your db context.

Can you examine your db context class inherit from ISaasDbContext or not?

[ReplaceDbContext(typeof(IIdentityProDbContext))]
[ReplaceDbContext(typeof(ISaasDbContext))] //ensure this line is exists
[ConnectionStringName("Default")]
public class MyDbContext : 
        AbpDbContext<MyDbContext>, 
        IIdentityProDbContext,
        ISaasDbContext //ensure this line is exists
{
    //...
}

You're welcome. I am closing the question since your problem is resolved.

Can you check your YourEntityFrameworkCoreModule depend on AbpSettingManagementEntityFrameworkCoreModule?

//other dependent modules
[DependsOn(typeof(AbpSettingManagementEntityFrameworkCoreModule))] //check this line exists or not
public class YourEntityFrameworkCoreModule : AbpModule
{
    //...
}

[ReplaceDbContext(typeof(IIdentityProDbContext))]
[ReplaceDbContext(typeof(ISaasDbContext))]
[ConnectionStringName("Default")]
public class YourProjectDbContext : 
    AbpDbContext<YourProjectDbContext>, 
    IIdentityProDbContext,
    ISaasDbContext
{
    //...
    
    protected override void OnModelCreating(ModelBuilder builder)
    {
        base.OnModelCreating(builder);
        builder.ConfigureSettingManagement(); //check this line exists or not
        
        //other configurations (e.g. builder.ConfigureAuditLogging())
    }
}

Hi @radhikashrotre, what is your ABP Framework version?

Did you define claims for the user that try to login passwordless, like here? These claims are required for user and role specific permissions.

Hi @viswajwalith, there is a community article about passwordless authentication, you can read from here. Can you check it and ensure there are not any steps that you missed?

Hi @david.hurtado, please wrap your create and update methods with try-catch blocks and handle exception by yourself (by using HandleErrorAsync method). => https://support.abp.io/QA/Questions/1523/Blazor-Server-ABP-Exception-Dialog-not-shown#answer-7939465b-3349-3100-2cc1-39fd4fd8c78a

And also, you can check the validations (are granted or not) inside of your create and update methods.

private Validations NewSalesmanValidations { get; set; } //validation that used in your create modal

//...

private async Task CreateNewSalesmanAsync()
{
   try
   {
      //if all validation rules are not validated, simply don't do anything  
      if (NewSalesmanValidations?.ValidateAll() == false) 
      {
         return;
      }
   
      await SalesmanAppService.CreateAsync(NewSalesman);
      await GetSalesmanAsync();
      CreateSalesmanModal.Hide();
   }
   catch (Exception ex)
   {
      await HandleErrorAsync(ex); //handles the exception and prevent app crash
   }
}