Activities of "MartinEhv"

Verions:** 8.3.2** Blazor Web App / Hybrid MASTER > CHILD Templating : 2 problems 1-N and N-N Relation

Building a 1-N and N-N Relation is fine. If you add a relation to the master after the child is built you get a series of errors. In a recent version i'm confident I was able to do this with only the Blazor template error, not DTO error. The DTO error seems new. (maybe I need to reboot, i dunno.. buti've tested 3 times now)

  1. Create normal Master record in the Suite. 1b) Save generate build
  2. Create a child linked to the master. 2c) Save, generate build
  3. Go to the Master. Add a N-N relationship 3B Build will fail.

ISSUE 1: BLAZOR TEMPLATE missing closing /Content and /Tabs tags

ISSUE 2: DTO not being generated correctly.

These behaviors ONLY happen when you create the 1-N/N-N AFTER the child relation.

For me is 3) Web App/ Hybrid which i think the original poster of this ticket @DHILL is asking.

  • UI Type: Blazor WebApp(hybrid server and wasm)

  • Ability to set template for CRUD N-N Navigation collections -- so that may define <select> (versus the Autocomplete that is currently default).

Without it: it means it means will cost a lot of manual labor to go and override the control at the last minute. And means that for every CRUD refresh, we loose the UI fix and have to go-re-fix it interrupting flow and losing fluidity.

Can i get some +1 upvotes on this?

Is this about the lower menu bar ? Copyright, About, Privacy, Contact links? I have been unable to modify those templates as well, nor find them in the codebase.

Neither of the _Footer.cshtml files in /Themese/Leptonx/Layouts/Account or /Application have any affect on the application. I remain with the standard copyright footer. The templates are not in affect.

Perhaps this is what DHILL asks? @DHILL??

Showing 1 to 4 of 4 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 01, 2024, 05:35