- Exception message and full stack trace: The name 'xxxCollection' does not exist in the current context
- Steps to reproduce the issue: Blazor CRUD Page generator to create two 1-n connections where the Dependent entity is the same
When creating the connection, I need to modify the Property Name and Collection name values to be created. This can be found in the Advanced tab at point 3. This works correctly.
In the resulting xxx.razor.cs file, only the first collection is created. The references are there, only the collection is missing.
Manually creating it works, but every update deletes it again.
Also, only one entry is created from GetxxxCollectionLookupAsync, where xxx is the original Entity name, not the renamed one, so only one field works in the create and update modal windows.
While this is not a bug, it would also be nice if the navigation properties could be set to appear on Create and/or Update modalities.
Best Regards,
Laszlo Szabados
3 Answer(s)
-
0
hi
We will check this case in the Suite.
Thanks.
-
0
Hello!
Another bug with Suite. When creating a child entity, if the Entity property has a min and max value, the {MasterEntityName}Consts class does not create the min and max values. Also, in the {EntityName}AppService class, the {EntityName}CreateDto and {EntityName}UpdateDto are missing the Annotations attributes.
However, the validation part of the UI declaration references the conditions.
Br
Laszlo
-
0
Hello!
Another bug with Suite. When creating a child entity, if the Entity property has a min and max value, the {MasterEntityName}Consts class does not create the min and max values. Also, in the {EntityName}AppService class, the {EntityName}CreateDto and {EntityName}UpdateDto are missing the Annotations attributes.
However, the validation part of the UI declaration references the conditions.
Br
Laszlo
Thanks for reporting the problem. I'll create an internal issue for your finding.
Regards.
