Thanks enisn, I'll work through these.
Thanks, we will be waiting for your reply.
Regards.
Hi, when you create a new ddd module template with new ABP Studio CLI (with abp new-module Acme.BookStore -t module:ddd -u angular command), then it gets the related template from Volo.Abp.Studio.Extensions.StandardSolutionTemplates NuGet package, so it's normal that the related file it's not same within the file in the link you shared.
Best regards.
Thank you four your quick response. When you say "update the MongoDbRepository" what do you mean? Could you provide an example?
Thanks again
Hi, for your generated entity there should be a MongoDB repository implementation, and in that class, there is an ApplyFilter method, you can update that method if you want to customize the sorting logic. But by default, we normally disable sorting for navigation properties, so it seems we forgot to do that for blazor-server side. We will check and fix it asap.
Regards.
Hi, can you try the following configuration and let me know if it works for you?
Configure<AbpAntiForgeryOptions>(options =>
{
options.TokenCookie.SecurePolicy = CookieSecurePolicy.Always;
});
Hi, can you please check our Change Microservice project to use MongoDB Provider documentation and follow the described steps, and see if it works for you? If you stuck at any point, please let me know.
Best regards.
Hi, in your data seeder, you should use ICurrentTenant.Change method to change the current tenant, otherwise, it will see the current tenant as host. Please refer to https://abp.io/docs/latest/framework/architecture/multi-tenancy#change-the-current-tenant, and if you can't work it out, then please share the data seed contributor so I can better assist you.
Best regards.
Note we have main app and HR module, when we generate entity int HR module gave me that error,
but when generate entity in main app, its work well without any errorsI will deeply investigate this, but ideally it should not give build error because as written in the logs it runs the following command:
dotnet build "C:\Mywork\ManarahTech\NeuErp\modules\HR"I'll let you know after checking it deeply.
Regards.
Hello bro.
It’s working well now. The issue is that the test project is unloaded because it targets .NET 7.0, which is not installed on our system.
Okay, great to hear that. Closing the issue, since your problem is resolved.
Best regards.
Hi @EngincanV, I understand that I can wrap each endpoint in a try-catch block to handle unexpected errors, but that would be time-consuming for us. Is there a way to centrally handle unexpected errors and return a specific error code and message?
ABP already has a built-in mechanism for global exception handling so you don’t have to wrap each endpoint in a try-catch block. ABP automatically handles all exceptions and sends a standard formatted error message to the client for an API/AJAX request.
But in your case, since it does not met the exception handling criteria it's not handled by ABP. So, you can subscribe to all of the thrown exceptions by implementing the ExceptionSubscriber base class, as described here. You can apply your own logic for the thrown exceptions.
Note we have main app and HR module, when we generate entity int HR module gave me that error, but when generate entity in main app, its work well without any errors
I will deeply investigate this, but ideally it should not give build error because as written in the logs it runs the following command:
dotnet build "C:\Mywork\ManarahTech\NeuErp\modules\HR"
I'll let you know after checking it deeply.
Regards.
You mean remove our solution from abp suite ?
Yes, and then re-add it again. This will refresh the solution info for your project. The pre-generated entity metadata will not be removed, so it will not create any problem.
Regards.
