I close the question since your problem seems to be related to inconsistent versions of ABP Suite and ABP. Feel free to re-open it if the answer above does not fix your problem.
Regards.
Hi, yes you are right the other filters should also be passed to the parameter and the filtering should work for them as well. I have created an internal issue (#15729) for this and will fix it asap.
Also, is it not wiser to use a POST request rather then a GET because the query parameters in a GET requests has a 2048 character limit and could possibly go over if i have enough filters?
I understand your intent but since we are getting a result back and not adding or updating any record to a datastore, and instead just collecting the result and returning it GET request seems more proper, according to REST API guides.
I could not reproduce the problem that you stated:
Your ABP Suite version and your ABP version must be the same to generate code successfully and not miss a code template. So, please check they are in the same version. Probably your .dll files are not up-to-date and they are in v7.4.1, so you can delete bin/obj folders and build your project. You can check this answer for more information.
Hi, I will check this and write you back asap.
Hi, thanks for reporting this problem. We have already identified this problem and it will be available with the next release (v7.4.2 or v8.0.0 - depending on the next release):
I closed the question since the problem you have reported has been fixed and will be available with the next release. Thanks for your understanding.
Btw, I have refunded your ticket. Regards.
Hi, thanks for reporting this problem. We have already identified this problem and it will be available with the next release (v7.4.2 or v8.0.0 - depending on the next release):
I closed the question since the problem you have reported has been fixed and will be available with the next release. Thanks for your understanding.
Btw, I have refunded your ticket. Regards.
Hi, thanks for reporting this issue. We have fixed it and it will be available with v7.4.2 or v8.0.0 (depending on the next release):
I close the question since the problem you have reported has been fixed and will be available with the next release.
Btw, I have refunded your ticket. Regards.
APB Team; The reason I believe this to still be a bug is because: A: The ABP Suite generates the .extended.cs class for existing projects when you check the Customizable Code checkbox. But, it's only half complete. It does not regenerate the pages and javascript files correctly. The .cshtml pages get regenerated but there are no @//<suite-custom-code-block-x>@ @//</suite-custom-code-block-x>@ tags. Why regenerate the main class and create the .extended.cs file if you are going to neglect to regenerate the cshtml and javascript code without the custom code blocks? The same for the javascript files.
//<suite-custom-code-block-x> //</suite-custom-code-block-x> blocks are not generated in the freshly regenerated javascript code. It leaves the solution half-baked. Can this issue be fixed? Also, it really shouldn't be counted against my support questions.
Thank you for looking into this.
Thanks for the explanation. I will create an internal issue for this and I have refunded your ticket. Closing the issue...
Best regards.
Hi, currently this is not possible by editing templates. Instead, if it's possible you can update your application to v7.4.0, re-generate the related entity with custom code support, and make the related customization in your *Entity.Extended.cs class in your domain layer.
See the blog post for more information (Suite: Custom Code Support section).
In the article you describe: < > In this version, ABP Framework provides base classes and events to migrate the database schema and seed the database on application startup. This system works compatibly with multi-tenancy and whenever a new tenant is created or a tenant's database connection string has been updated, it checks and applies database migrations for the new tenant state.
This system is especially useful to migrate databases for microservices. In this way, when you deploy a new version of a microservice, you don't need to manually migrate its database.
You need to take the following actions to use the database migration system:
Create a class that derives from EfCoreRuntimeDatabaseMigratorBase class, override and implement its SeedAsync method. And lastly, execute the CheckAndApplyDatabaseMigrationsAsync method of your class in the OnPostApplicationInitializationAsync method of your module class. Create a class that derives from DatabaseMigrationEventHandlerBase class, override and implement its SeedAsync method. Then, whenever a new tenant is created or a tenant's connection string is changed then the SeedAsync method will be executed.
I like to see a practcal implementation how to implement the described steps in a MVC application.
Hi, here is the issue of this feature: https://github.com/abpframework/abp/pull/16862
You need to do the steps mentioned in the issue and then execute the CheckAndApplyDatabaseMigrationsAsync method of your class that derives from the EfCoreRuntimeDatabaseMigratorBase class in the OnPostApplicationInitializationAsync method of your module class:
Limited Time Offer!
