that's mean that i should re-do the hole solution from scratch
what if i already have a project running with UI and all is good but i want to make some relations and pages using ABP Suite?
In the current structure of the master-child relationship of ABP Suite, yes you should re-configure these three entities.
But if your only purpose is to show the parties and addresses in the row detail view, then you can create a separate solution, establish a master-child relationship with these entities, and apply the "row detail view" codes in your own application. This seems a better approach for you, with this approach, you'll just define some application service methods, and apply the UI changes.
Hi, in your code PartyAddress
is a join entity (join-table in the database term) and its only responsibility is to establish many-to-many relationship between Party
and Address
entities. Therefore, I'm not sure it's a good candidate for a master-child relationship.
In a master-child relationship, you would ideally have an entity and its data that can be considered as details of it. For example, you may have a customer entity and its contact information, in that scenario, you can define a master entity named Customer
as a master entity and a Contact
entity as a child entity and associate it with the master entity.
So, the master and child entity should have a key to establish a relationship and that means the master entity should have a unique identifier (Id
) and in your case, since the PartyAddress
is the join entity, you can't create a master-child relationship with it.
finally figured it out for anyone else experiencing the same issue.
- using visual studio, Build > Clean Solution
- in the root folder of your source code run: abp clean
- using visual studio, Build > Rebuild Solution
- after closing the abp suite, reload the abp suite and reopen your solution
To be able to generate CRUD pages, it's always good to stop your application if it's running. Otherwise, files may be locked therefore may not be changed.
I close the question, since your problem should be resolved. Feel free to re-open if it still persists.
Best regards.
I have also just compared my suite templates to that of my team members and mine are not the same. It appears the attempted upgrade to 8.0.1 and then downgrade, didnt reset the code templates. How do I reset these? I have uninstalled and reinstalled abp cli and suite numerous times to resolve with no luck. I would like to just reset the code generation templates to v7.3.2
If you want to go back to v7.3.2, then you should uninstall CLI and Suite and then re-install again (make clean uninstall).
dotnet tool uninstall -g Volo.Abp.Cli
dotnet tool install -g Volo.Abp.Cli --version 7.3.2
BTW, there is not a problem in ABP Suite that prevent removing these placeholders, if you make a clean uninstall and then upgrade both your CLI and Suite to v8.0.1, then you should be able to generate CRUD pages without worrying about these problems. It seems there are missing parts in your Suite installation or ABP CLI and ABP suite versions are not same.
Hi, sorry for the late response. I have identified the problem and fixed it. It will be included in v8.0.2, I'll let you know when it's released.
Btw, your ticket is refunded. Best Regards.
Hi, thanks. I have checked and reproduced the problems that you mentioned.
Blazor.Server.Host:
OnInitializedAsync
method to be able to get the rule systems in the select box in the advanced search section: protected override async Task OnInitializedAsync()
{
await SetToolbarItemsAsync();
await SetBreadcrumbItemsAsync();
await SetPermissionsAsync();
//add the line below
await GetRuleSystemCollectionLookupAsync();
}
This has already been fixed and will be available with v8.1.
Web.Unified:
✅ Correct one: window.yee.change.rms.public.ruleGroups.ruleGroup.getRuleSystemLookup;
LookupModal.cshtml
(under Pages/Shared folders):<div id="NavigationPropertyLookupTableModal">
<abp-modal size="Large">
<abp-modal-header title="@(L["Pick"].Value)"></abp-modal-header>
<input hidden id="CurrentLookupId" value="@Model.CurrentId" />
<input hidden id="CurrentLookupDisplayName" value="@Model.CurrentDisplayName" />
<abp-modal-body>
<abp-table striped-rows="true" id="LookupTable">
</abp-table>
</abp-modal-body>
<div class="modal-footer">
<button id="CancelButton" type="button" class="btn btn-secondary" data-bs-dismiss="modal">@L["Cancel"]</button>
</div>
</abp-modal>
</div>
Any news about the fix? It's not possible to use ABP Suite with the last version to create a new module
https://github.com/abpframework/abp/pull/18702
With this PR, it will be fixed and will be included in the next release. In meantime, if it's so urgent for you to create a template, then you can consider to downgrade the ABP CLI and ABP Suite versions to v8.0.0.
Hi, the application was not running, turned off the antivirus and created a new abp application from ABP Suite and still got that error.
Thanks. I have addressed the problem and create a PR for it: https://github.com/abpframework/abp/pull/18702
There is an important error in ABP Suite for 8.0.1.
Can't create a module even in a clean installation.
You get the following error while creating a new module
Please, this requires special attention to be fixed soon and this shouldn't happen in future versions since it's a basic functionality of ABP Suite
Thanks.
Hi, can you check if your application is running or not? If it's running please stop it and then re-try to add the module.
Hello @szhongfang,
I am trying to reproduce the issue but am unable to do so. Could you please share your application on support@abp.io with the ticket number so that we can better assist you?
Or if you are unable to share your project, then please share the entity details. (both RuleGroup
and RuleSystem
entities and .suite/entities folder in your application)