For years we have been using the MVC (Razor) UI, where we added extended properties to Users, Organization Units and Tenants. In Razor they appear in the forms automatically and everything works fine.
We are now migrating our application to React, and we see that the Admin Console is a separate application. There, our extended properties are not shown at all — not in the create form, not in the edit form, not in the tables. As a result, users, organization units and tenants can no longer be created or edited: every save fails with validation errors of the form "The <PropertyName> field is required", because the form never sends those values.
Our questions:
- Do you plan to support extended properties in the Admin Console, and roughly when?
- If not, is there another solution you would recommend?
Thank you.
4 Answer(s)
-
0
ABP Admin Console (React) does not currently auto-render your module/entity extensions (extended/extra properties) on the built-in management screens (Identity Users, Organization Units, Saas Tenants). That’s why:
- the fields don’t appear in create/edit forms and grids
- the backend still validates them as
Required, so saves fail because the Admin Console never posts those values
Roadmap / “when”
- I don’t have a verified public source that states if/when the Admin Console will support rendering extended properties for these built-in pages. No verified source available for a timeline for this specific query.
Recommended solutions
Do not use Admin Console for those specific create/edit flows. Build your own pages in your developer-owned React app (the one generated in your solution), where you can fully control the forms and include your extended properties.
- This aligns with ABP’s positioning: the Admin Console is ABP-managed and intended to be updated by upgrading packages; for larger/custom UI needs you should prefer your own app pages.
- Practically: create your own “Users / Tenants / OUs” pages, call the same backend endpoints (or your own wrapper AppServices), and include
extraProperties/ your extended fields in the DTO you send.
Backend-side mitigation (only if you must keep Admin Console temporarily): make those extended properties non-required or provide defaults
- Remove/relax
[Required]on the extension definition, or provide aDefaultValuein the extension configuration so the server can accept requests that don’t include those fields. - This is a compromise: you’ll lose UI enforcement until your custom UI posts the values.
- Remove/relax
If you want “automatic UI” for extended properties, use a UI that already supports it for those module pages
- Your observation matches typical behavior: MVC Razor UI can auto-generate extension fields on module pages; Admin Console currently doesn’t.
- If automatic rendering is a hard requirement, staying on MVC Razor for admin management pages (or moving to another ABP UI that supports object extension rendering for those pages) is the safer approach.
Sources:
- https://abp.io/docs/10.6/framework/ui/react/admin-console
- https://abp.io/docs/10.6/framework/ui/react/customization
- https://abp.io/community/articles/rixchoha
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
The Admin Console doesn't render module extension properties yet. Its user, organization unit and tenant forms post a fixed set of fields, so your extra properties never reach the server and the required validation rejects the request.
We're adding support for this, planned for a release after 10.7. The built-in Identity, organization unit and Saas tenant screens will then read your extension definitions and render them on the create/edit forms and in the tables, including the validation attributes you configured.
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
