Activities of "EngincanV"

With version 8.0.2 (MVC) Abp suite creates a function like below for master-child data. When I click the details button on datatable it shows an error. Because childB in data.childB.id is null at first.

    function initDataGrids(data) { 
        initChildAGrid(data) 
        $("#ChildBs-tab-" + data.childB.id).one("click", function (e) { 
            initChildBGrid(data); 
        }); 
    } 

But i think it should be like below

    function initDataGrids(data) { 
        initChildAGrid(data) 
        initChildBGrid(data); 
    } 

After these changes there were a datatable column width issue on selecting the non visible tab. Making below changes resolved this issue.

    function initDataGrids(data) { 
        initChildAGrid(data) 
        initChildBGrid(data); 
        document.querySelectorAll('a[data-bs-toggle="tab"]').forEach((el) => { 
            el.addEventListener('shown.bs.tab', () => { 
                DataTable.tables({ visible: true, api: true }).columns.adjust(); 
            }); 
        }); 
    } 

Initializing the child data grids once should be enough actually, but I'll check this one.

At master-child cretion I would like to set add and update migrations instead of suite tries to do it immediately.

We made an enhancement and from now on the child entity will respect the selection of the master entity and will create a new migration if it's enabled for the master entity, otherwise, it won't create a new migration and apply it.

https://support.abp.io/QA/Questions/3052/Your-feature-request#answer-3a0d62be-d186-9460-0995-e613ddc33fbf

I would like the advanced filter to be generated optionally (for all UI types)

Thank you

I'm happy to announce that we are going to support that with v8.1 🎉

Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): The INSERT statement conflicted with the FOREIGN KEY constraint "FK_AppInvoiceDetails_AppInvoices_InvoiceId". The conflict occurred in database "InvoiceSample_SQL_Server_2022", table "dbo.AppInvoices", column 'Id'.

Hi, it seems it's not related to the generated code, instead, it's related to the current database state. It says it's violating the foreign key restriction, so please revise the entity configuration.

I have updated ABP Suite from the server (for this bugfix), so please follow the below steps:

1.) Uninstall ABP Suite:

dotnet tool uninstall -g Volo.Abp.Suite

2.) Clear NuGet caches:

dotnet nuget locals all --clear

3.) Re-install ABP Suite:

abp suite install --version 8.0.2

Then, when you regenerate the entity, it should work as expected.

Hi, it seems it's not looking in the correct directory. I'll recheck it again in the code.

Hi, you can check the documentation to add the IdentityUser as the np.

We enhanced this flow and with v8.1, you'll be able to select it from the basic tab, but if you need to do it now, you can follow the documentation.

Thank you, but the main problem is the error in the DataGrid and not the migration ;-) But I assume you created a bug for that too.

Yes, in the issue that I created, I mentioned these two problems :)

With the child, there is no option to deactivate the DB migration. If you don't want this for the master, then you don't want it for the child either. In addition, because of the above error, it naturally means that a migration can never be created because of the error in the DataGrid.

Hi, yes you are right, the child entity should respect the master entity's option for migration creation. I have created an internal issue (#16434), and fix it asap.

I have refunded your ticket, thanks for reporting these problems. Closing the question.

Best regards.

Thank you for fixing this.

Could you please refund the ticket? Thanks.

Sure, I have refunded your ticket and closed the question.

Best Regards.