Modular development with Abp Suite encountered an exception => The entity type 'ExtraPropertyDictionary' requires a primary key to be defined. #9317

4 Answer(s)

• 

  0

  enisn created one month ago

  Support Team .NET Developer

  It seems it cannot configure entity base properties in DbContext or the extension method of the module.

  Can you check AbpModularSolution1DbContext and find OnModelCreating() method in it.

  Is there any method that configures your module something like ConfigureTestModule()

      protected override void OnModelCreating(ModelBuilder builder)
      {
          base.OnModelCreating(builder);
          
          // ...
          
          builder.ConfigureTestModule(); // 👈
      }
  

  If yes, go to your module solution and find that ConfigureTestModule method and make sure your entity is configured properly and calls .ConfigureByConvention() method in entity builder.

  public static void ConfigureTestModule(this ModelBuilder builder)
  {
      // ...
  
      builder.Entity<Hello>(b =>
      {
          b.ToTable(TestModuleConsts.DbTablePrefix + "Books",
              TestModuleConsts.DbSchema);
              // 👇 Make sure this is called.
          b.ConfigureByConvention(); //auto configure for the base class props
      
      });
      
      // ...
  }
  

  This method configures ExtraPropertyDictionary to be kept as string as json in the databse and that exception will be gone

  Save Cancel
• 

  0

  15021087273 created one month ago

  I followed your instructions to check the code and it meets the requirements. The following are two code blocks： 1)OnModelCreating

  [ConnectionStringName(TestModuleDbProperties.ConnectionStringName)]
  public class TestModuleDbContext : AbpDbContext<TestModuleDbContext>, ITestModuleDbContext
  {
      public DbSet<Hello> Hellos { get; set; } = null!;
      /* Add DbSet for each Aggregate Root here. Example:
       * public DbSet<Question> Questions { get; set; }
       */
  
      public TestModuleDbContext(DbContextOptions<TestModuleDbContext> options)
          : base(options)
      {
  
      }
  
      protected override void OnModelCreating(ModelBuilder builder)
      {
          base.OnModelCreating(builder);
  
          builder.ConfigureTestModule();
      }
  }
  

  2)ConfigureTestModule

  public static class TestModuleDbContextModelCreatingExtensions
  {
      public static void ConfigureTestModule(
          this ModelBuilder builder)
      {
          Check.NotNull(builder, nameof(builder));
  
          /* Configure all entities here. Example:
  
          builder.Entity<Question>(b =>
          {
              //Configure table & schema name
              b.ToTable(TestModuleDbProperties.DbTablePrefix + "Questions", TestModuleDbProperties.DbSchema);
  
              b.ConfigureByConvention();
  
              //Properties
              b.Property(q => q.Title).IsRequired().HasMaxLength(QuestionConsts.MaxTitleLength);
  
              //Relations
              b.HasMany(question => question.Tags).WithOne().HasForeignKey(qt => qt.QuestionId);
  
              //Indexes
              b.HasIndex(q => q.CreationTime);
          });
          */
          if (builder.IsHostDatabase())
          {
  
          }
          if (builder.IsHostDatabase())
          {
              builder.Entity<Hello>(b =>
              {
                  b.ToTable(TestModuleDbProperties.DbTablePrefix + "Hellos", TestModuleDbProperties.DbSchema);
                  b.ConfigureByConvention();
                  b.Property(x => x.Name).HasColumnName(nameof(Hello.Name)).IsRequired().HasMaxLength(HelloConsts.NameMaxLength);
                  b.Property(x => x.Description).HasColumnName(nameof(Hello.Description));
                  b.HasOne<IdentityUser>().WithMany().IsRequired().HasForeignKey(x => x.IdentityUserId).OnDelete(DeleteBehavior.NoAction);
              });
  
          }
      }
  }
  

  Is it caused by the development environment? My Abp Suite version is v9.1.1

  Save Cancel
• 

  0

  15021087273 created one month ago

  AbpModularSolution1DbContext Code:

  [ReplaceDbContext(typeof(IIdentityProDbContext))]
  [ConnectionStringName("Default")]
  public class AbpModularSolution1DbContext :
      AbpDbContext<AbpModularSolution1DbContext>,
      IIdentityProDbContext
  {
      /* Add DbSet properties for your Aggregate Roots / Entities here. */
  
  
      #region Entities from the modules
  
      /* Notice: We only implemented IIdentityProDbContext 
       * and replaced them for this DbContext. This allows you to perform JOIN
       * queries for the entities of these modules over the repositories easily. You
       * typically don't need that for other modules. But, if you need, you can
       * implement the DbContext interface of the needed module and use ReplaceDbContext
       * attribute just like IIdentityProDbContext .
       *
       * More info: Replacing a DbContext of a module ensures that the related module
       * uses this DbContext on runtime. Otherwise, it will use its own DbContext class.
       */
  
      // Identity
      public DbSet<IdentityUser> Users { get; set; }
      public DbSet<IdentityRole> Roles { get; set; }
      public DbSet<IdentityClaimType> ClaimTypes { get; set; }
      public DbSet<OrganizationUnit> OrganizationUnits { get; set; }
      public DbSet<IdentitySecurityLog> SecurityLogs { get; set; }
      public DbSet<IdentityLinkUser> LinkUsers { get; set; }
      public DbSet<IdentityUserDelegation> UserDelegations { get; set; }
      public DbSet<IdentitySession> Sessions { get; set; }
  
      #endregion
  
      public AbpModularSolution1DbContext(DbContextOptions<AbpModularSolution1DbContext> options)
          : base(options)
      {
  
      }
  
      protected override void OnModelCreating(ModelBuilder builder)
      {
          base.OnModelCreating(builder);
  
          builder.ConfigureTestModule();
  
          /* Include modules to your migration db context */
  
          builder.ConfigurePermissionManagement();
          builder.ConfigureSettingManagement();
          builder.ConfigureBackgroundJobs();
          builder.ConfigureAuditLogging();
          builder.ConfigureFeatureManagement();
          builder.ConfigureIdentityPro();
          builder.ConfigureOpenIddictPro();
          builder.ConfigureLanguageManagement();
          builder.ConfigureFileManagement();
          builder.ConfigureChat();
          builder.ConfigureTextTemplateManagement();
          builder.ConfigureGdpr();
          builder.ConfigureBlobStoring();
          
          /* Configure your own tables/entities inside here */
  
          //builder.Entity<YourEntity>(b =>
          //{
          //    b.ToTable(AbpModularSolution1Consts.DbTablePrefix + "YourEntities", AbpModularSolution1Consts.DbSchema);
          //    b.ConfigureByConvention(); //auto configure for the base class props
          //    //...
          //});
      }
  }
  

  Save Cancel
• 

  0

  enisn created 23 days ago

  Support Team .NET Developer

  Whenever you create a new project there'll be already a file for that purpose with an example:

  • For Module extension:

  • And Entity extension: (if you choosed EntityFrameworkCore)

  ---

  You can uncomment that examnples and ready to go, there'll be no other changes. If you configured any EntityExtension, you'll need to create a database migration.

  If you are not familiar with CLI commands you can do it in ABP Studio UI:

  And that's it you'll see the new migration:

  • Run .DbMigrator project

  • Run .Web project

  

  Save Cancel