Hi Anjali,
Storage size is set to 0 (i.e unlimited) in FileManagement settings and the provided link it wasn't very helpful.
Thanks & Regards, Yulian
Hi Anjali,
I am closing this issue, because I've found out that the problem was on kubernetes nginx ingress controller. By default the size is limited up to 1M. So the following annotation needs to be set: nginx.ingress.kubernetes.io/proxy-body-size.
Thanks, Yulian
Hi Anjali,
It's not working as well. Actually the same error appier if you will generate a new project based on a microservice template with Blazor WASM by abp suite v7.4.0.
Cheers, Iulian
Hi,
What do you mean data result is correct? The problem is that I request wrong filtering conditions from the backend. On UI you see one date, but the backend results will be provided based on different dates.
Hi,
Actually I've searched for date ranges DateMin and DateMax. For DateMin is not a problem because the 17.10.2023 is less than 18.10.2023, but for DateMax if I use 18.10.2023 then the api request will contain the interval between 17.10.2023 and 17.10.2023. That means that the records with date 18.10.2023 will not be returned. In such way filtering will not work properly.
Steps to reporduce:
I hope I am more explicit now.
Thanks
Hi,
It's very simple. You can take any project you have or generate the entity with abp suite. It is important that the entity has a one-to-many relationship with another entity so that LookupDto appears in Api. Then generated as usual static proxy clients. For the entities that have Lookups, errors will appear, in the order of those in the image presented later.
Hi,
Apparently everything is fine with ElasticSearch. No log errors.
Cheers, Iulian
If you have not encountered such an error recently, then I will close the this issue.
Hi,
Thanks for giving me a clue. I've probably understood where the mistake could be. Just after your suggestion, I've noticed that when adding a new microservice to the solution, in the file with the constants in my case AcquisitionServiceRemoteServiceConsts from the Application.Contracts project, the variable with the name of the module is not added, that is, the following declaration is missing public const string ModuleName = "acquisitionService"; And for this reason, the controllers do not appear in the api definition, because each controller has the [Area("acquisitionService")] attribute. So please check the generation of the files in case of the addition of the microservice to the solution.
Thanks Iulian
Probably this is specific to my infrastructure configuration. I'll close the issue.
