I appreciate you Quick replay ,but i would like to make master detail like this sample After i add header data and save the header
the Add button in detailed grid enabled and add data in grid
all of that and i still in the same page
Unfortunately, we are not providing a UI like you shared out of the box, and as you would understand we are only providing a general detail row template for the master/child relationship. Therefore, if you need a page design as you shared, then you can first use ABP Suite's Master/Detail Relationship feature, and wait for it to apply the related changes and design and then you should change the UI by your needs.
Note: We are considering building form builder in the future and that means this can be supported in the future.
Hi, I could not reproduce any one of your findings:
I guess, you probably have an extension, which prevents opening modals twice for a certain element or you modified the generated code and this cause these problems (you may have a custom js code that causes these problems).
So, please check the console logs and the custom scripts in your application, and also try to reproduce this in a private window.
Hi, ABP Suite allows you to create a master-detail relationship with a few clicks.
An example output:
Please check the documentation: https://docs.abp.io/en/commercial/latest/abp-suite/creating-master-detail-relationship
Thanks for the comprehensive explanation but as you would understand there is nothing we can do at that point. This is not related to ABP Suite itself, but the database provider and the SQL server itself.
Hi, Thanks for quick response and help.
It is already clearly written in the document your team "@maliming" shared with me, EF Core 8 version no longer supports SQL Server 2014 and below.
https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-8.0/breaking-changes#high-impact-changes
New behavior Starting with EF Core 8.0, EF now generates SQL that is more efficient, but is unsupported on SQL Server 2014 and below.
It's clear that you have nothing to do about this. For now, we will continue to develop and work on the application with the old version abp (below version 8).
Thank you for your support
Best regards
Thanks for your understanding. I'll add this to our documentation. Best regards.
Thanks for the comprehensive explanation but as you would understand there is nothing we can do at that point. This is not related to ABP Suite itself, but the database provider and the SQL server itself.
Hi again,
I installed Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64) Express Edition (64-bit) and it worked in this version.
CompatibilityLevel 160
I understand that you have to use SQL Server CompatibilityLevel (160) in ABP Framework 8 version (abp suite and cli) , is this correct?
Changing the SQL server version at the customer location is not an easy thing, most customers will want to continue using their existing licenses. Can there be another solution to this?
Best regards
Hi, actually you would not need to set the compatibility level manually to 160 if the server would not be a local SQL server (it works as expected for other server types), I'm not sure why this is happening but I'll investigate it and take the related action (it seems there might be a bug in EF Core 8, but I'll check it deeply). And also I'll let you know about the problem and the solution.
Best regards.
I have opened a PR to fix this problem:
2024-01-11 17:44:13.980 +08:00 [ERR] An error occurred while saving the entity changes. See the inner exception for details. Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): INSERT 语句与 FOREIGN KEY 约束"FK_AppFlowingReports_AppProjectFlowings_ProjectFlowingId"冲突。该冲突发生于数据库"ProjectReward"，表"dbo.AppProjectFlowings", column 'Id'。 语句已终止。
From the stack trace, it seems it can't add a record because it violates foreign key constraint, please check your entity configuration and the database.
Hi, I could reproduce the problem that you mentioned and created an internal issue for it. This occurs if your master entity has a name such as EntityA (I mean a pascalcase name). For a quick workaround, you can search in your application the word $(this).data("<yourentityname>-id") and replace the <yourentityname> placeholder with your entity name as lowercase.
BTW, I refunded your ticket, thanks for reporting this problem.
Hi, as far as I understand this problem occurs either because you are using a local SQL server or a lower SQL server version. You can try to set the CompatibilityLevel as 120 and try again: https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-8.0/breaking-changes#mitigations
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.
