Activities of "EngincanV"

From the last youtube podcast these are the most important features to us.

Bind to User Entities in ABP Suite Most important

We have implemented this one and it will be available with v8.1.

PDF export support Very important File/Image as a property type Uploads of multiple files on a record

For these two features, we have open internal issues but haven't prioritized them yet. File/Image as a property type feature might be implemented and released with v8.2.

Navigation Property: Current Behaviour: Only string properties are allowed!, UI pick type: 3 options New Behaviour: for non-string properties can we have 4th option for UI pick type: None and display property hidden.

I am not sure if it will be useful for general purpose or not.

We have an internal issue for allowing adding navigation property without a string display property and we aim to implement it with v8.2.

Hi, we have enhanced the flow to establish a relationship with entities of ABP modules in v8.1 and this problem will be fixed with v8.1. Thanks for reporting.

Regards.

Hi, this should have already been fixed. Please see the similar thread: https://support.abp.io/QA/Questions/6520/Error-when-adding-1-N-navigation-property-in-ABP-Suite-8

You probably need to make a clean uninstallation and then re-install ABP Suite to get the fixed version. Please follow steps mentioned at https://support.abp.io/QA/Questions/6520/Error-when-adding-1-N-navigation-property-in-ABP-Suite-8#answer-3a103316-d564-f4f0-b00b-a34fa1bc72d0

Hi, can you try to build your solution and share the build errors? Also, what is your exact ABP Version, v8.0.0 or different?

Will abp suite support child's child entity? If not while creating a child entity, child entities shouldn't be selectable at master entity selection dropdown.

Currently, we are not considering supporting it.

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.