OK yes, we are on 3.3.2 (CLI, Suite, and Solution), and yes the bin and obj have been cleared, and yes the character does appear in 2 templates, and yes the problem is still occurring.
We are definitely in v3.3.2
But sorry, I don't know where to find these TXT files you are referring to. I have grepped the solution folder and there are no *.TXT files.
I'm sorry, it isn't clear what you mean.
I understand that if I need to implement a base N:N relationship, I can hand-code it. But we purchased a license for ABP so we wouldn't have to do that.
What I am asking for is support for N:N relationships in ABP Suite (entity/CRUD generator).
And my original question was: Can you please tell us when it will be available?
The page at https://docs.abp.io/en/commercial/latest/abp-suite/generating-crud-page says:
Currently there's no support for many-to-1 (N:1) or many-to-many (N:N) relationships!
This is a major problem for us. Can you please tell us when it will be available?
MVC v3.3.2
I added a new entity with a one-to-many relationship. Even with no data, when I try to load the UI grid, I get this:
Your request is not valid! The following errors were detected during validation.
Even with good data (i.e. none of the rows have a null XXXXXId, I get the same error.
Unfortunately not all of the developers have the solution at the same path. We're looking forward to the new feature.
Ok, in fact this morning when I upgraded to 3.3.2 the problem seems to be mostly resolved. There is a build error relating to Microsoft.EntityFrameworkCore 3.1.6 but that is resolved by making the version 3.1.8.
This is a problem for me also. I uninstalled ABP Suite and re-installed. Same problem. My CLI and my Suite and my Solution are all at 3.3.1.
This is urgent because I am roadblocked on dev work and it is impacting a client committment!
Bug in ABP Suite
I updated my project to 3.3.1 but ABP Suite still says I am on 2.9.0. It also says I was active 4 months ago which is not true since I updated the project today.
Can I please get an update on the expected delivery date for the new feature referred to by @alper above?
