Hi @dweiss
Can you check the version of Volo.Abp.Commercial.SuiteTemplates package? Is it 7.2.2 too?
Have you overriden the domain manager template for this project?
Most likely you have overriden the template. Because normally CreateAsync and UpdateAsync method has return values in their signatures. Example:public async Task<AnotherEntityTest> CreateAsync. but in your case there are no <AnotherEntityTest> in the generated code.
I've checked the previous Suite versions and i could not find a version that generates these methods without return values. That is why i think you've overriden them.
To undo the override, go to Templates page in suite and revert the customization for Server.Domain.Manager.txt.
If you have never override the template, i will check again. For now i don't see any other reason than i explained.
Hi @epeters,
Is it microservice template or microservice-service template?
Hi @hinairusu,
It seems like Suite fails to find your solution's ABP version. We'll enhance the algorithm of that process in the next release. Thank you for reporting. Your question credit is refunded.
For a workaround: You can set the ABP version manually in %USERPROFILE%\.abp\suite\appsettings.json file. Then restart the Suite.
As @caglar.ayhan said, it is not possible to generate an entity without a property. And only way to workaround this is also explained by @caglar.ayhan.
We can not simply enable the generate button, because code generation process assumes that there are at least one property and without a property there will be compile errors on many places in the generated code. So we have to work on this if we want to allow generation without property.
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.
