Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
If you're creating a bug/problem report, please include followings:
- ABP Framework version: v6.0.0
- UI type: MVC
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace:
- Steps to reproduce the issue:"
Hi
My project also has a module application with nine entities.
I published to live system, and was working well. I have two databases. The shared database and a dedicated client database. This is the same for my local dev system, as well as the live system. All 9 entities work as designed.
I then used the ABP Suite v6.0.0 to add a new entity to a module application. A made all the business logic changes and added the required factuality.
I Added migrations and ran the app.DbMigrator project to update the 2 local databases The new data table was created correctly, for my local two databases The app worked as intended. When logged in as a Dedicated database tenant and a Shared database tenant.
All 10 entities worked on the local system.
I changed the connection string to my live system and ran the app.DbMigrator project which added the new data table on both databases. Bothe are identical. I then ran the application and logged in as a Dedicated Tenant Database, all 10 entities work as intended.
When I log in as a shared Database tenant, 9 entities work as intended, but the new entity reports the following error indicating that there is no data table with the name IntegrationBudgets When I run the application locally, with the SQL connection to the remote database or in the live environment, I get the same error. see attached file
When I log in with a Tenant with a dedicated database, I don't get the error
The two databases have identical data table design and structure.
I then tested with the local database, and all works as designed.
I then used the ABP Suite to rename one of the fields "GLCode" to SegmentAccount", and merged my other changes. The application now reports that the following: Microsoft.Data.SqlClient.SqlException : Invalid column name 'NewFieldName' for the IntegrationBudgets on the shared database tenant.
I updated all PackageReferences for Volo to version="6.0.3" and this did not fix the issue
Are you able to help