I think you can add properties to AssemblyPart. Of course you will need many changes in the generated code.
Hi @mikeolofernes,
Yes, we've made some changes about that.
I guess the latest code generation has overwriten the existing lookup dtos, and that caused code generated in Suite v6.0.0 to be broken. So, i can suggest you to rename the shared dtos and so they will not be overwritten, then you can generate code in Suite v7.0.3 version.
if we have TableA and TableB, and create n-to-n relation/navigation on both ends, it creates TableATableB TableBTableA
Suite only generates one of them. Not both.
Ideally it should be the same table
I didn't fully understand why you meant by "same table".
the UI on both would be updated to point to that same table/entity/dto? Best options?
We don't want generating a page affects an existing page. But you can copy the codes from one to other if you want the m-m selection in both UI.
Hi,
With 2.0.0 release, LeptonX theme is using net7.0. I guess your project is net6.0. So you need to specify the compatible version when adding the LeptonX package.
abp add-package Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX -v 1.0.3
H @chauey,
If we have n to n for Categories and Tags, we add Tags as n to n navigation for Categories? it will generate a tab to add Tags?
Yes, it will generate a tab in the create/update modals for you to add tags.
What about the UI for Tags? does it not also have a tab to add Categories?
Tags will not have a categories tab.
If we add n to n navigation of Categories to Tags, it will create an additional and separate table? Solutions?
It will create a separate db table to save the relation between categories and tags.
I've created an entity named book and then created an author entity with a navigation property to book entity. Tests are successful. See the screenshot below:
Is there anything extra that had to be done to reproduce this problem?
@Callum I've deleted the link in your reply since it may contain private data. I'll check this problem.
I've created an internal issue. Thank you for reporting.
@zhaof Thank you for reporting. I'll create an internal issue about that and fix it in next releases.
Your question credit is refunded.
