Thank you I believe the upgrades in installed took care of the issue
No option to Replace package with source code.
7.0.1. I have since uninstalled ABP suite with the same results. I really need this source integrated. Thank you
I hope this fix is quick, that's not and acceptable workaround as it will corrupt my entire database.
now, this is not the same error. my is
Volo.Abp.Identity.IdentityRole ValueBufferExpression: ProjectionBindingExpression: EmptyProjectionMember IsNullable: False , "Code")' failed. Either the query source is not an entity type, or the specified property does not exist on the entity type.
I should mention that the scenario does work up until CommunitiesAppService is alwasy null
more proper, I think anyone would have to agree. not?
If this is not something you're going to fix, can you give some guidance on where to fix it?
now I have a dilemma a real dilemma, do I really build out my database with this terrible design, or do I scrap the whole thing. entirely unacceptable 
modifying the migration file works fine but then the UI blows up
The fact that adding a many to many relationship that does not respect the schema of the parent table is absolutely a bug; opposed to your statement that it is not here
https://support.abp.io/QA/Questions/3381/BUG--CRUD-Generator-when-creating-a-Many-Many-table-does-not-respect-the-schema-name-of-the-app
debating using schemas aside, does this really look like good database design to you?
this is my entity configuration
builder.Entity<CommunityAgent>(b => { b.ToTable(DataManagementDbProperties.DbTablePrefix + "CommunityAgents", DataManagementDbProperties.SchemaCommunity); b.ConfigureByConvention(); b.HasKey(x => new { x.IdentityUserId, x.CommunityId }); b.HasOne<Community>() .WithMany() .IsRequired() .HasForeignKey(x => x.CommunityId) .OnDelete(DeleteBehavior.NoAction); b.HasOne<IdentityUser>() .WithMany() .IsRequired() .HasForeignKey(x => x.IdentityUserId) .OnDelete(DeleteBehavior.NoAction); });
