Activities of "MartinEhv"

Reproduction is 1/2 way there ;-). Note the screencaps of the "variable" missing during the forced debug. I think there is a hash/array that went out of bounds and everything breaks. Probably i went past original-designed upper bounds of "normal app use" and moved us in to edge/extreme. "128 fields, yeah! thats enough!". Nope.

This is a manufacturing floor Line-of-business app. The dashboard will-have literally 300 fields once pivoted.

Oh.. btw. .i'm continuing to onboard my entities. I have about 7 that have over 150 fields. and 2 with 256 fields. For now i'm just onboarding them without any filters enabled in the default constructors, nor then, thus, the default List pages built by CRUD, which is NOT the intent. But to get moving , thats what I'm doing until this detail is resolved.

Well yes. thats the point. i've ran many experiments already proving that it's the parameter limit. i've done this both manually and with constructing of the parameters via the Suite. So . no need for me to recreate - i've already done that test, at infinitum, before i submitted.

As stated, if you look closely at the GetCountAsync error.. when no filter is passed there is .. oddly, a filter being passed; with a iterator of 128. I suspect that either ABP, or something lower can not handle more than 128 variables. But as .mssql can(2000 parameters), Thus, I suspect ABP.

How can we definitively debug ABP. it should not be inserting the following whatsoever:

**WHERE [a].[Aaa128] <= @__aaa128Max_Value_0**

On a first-page load. This should not be there; and it's not if you have less than 127 fields.

Sent in test scaffolding project (not the actual project) showing the same issue.

Note: OSX, Apple M1

Note the signature of all filters being passed...

As for the JSON from Suite: All properties/fields 1-131 have isFilterable = true Just a simple Entity ( which is why audit logging confused me but could of still be possibility )

I've run this in my current large project as well as a new standalone 'host' app created from Studio Here is a basic Json i use in test... first 3 fields so you can see the basics without the whole code(i can't seem to attach the whole thing here)

{ "Id": "5a972b55-3bb5-4847-bd62-8d7b8cd49c74", "Name": "TestThree", "OriginalName": "TestThree", "NamePlural": "TestThrees", "DatabaseTableName": "TestThree", "Namespace": "TestThreeNs", "Type": 1, "MasterEntityName": null, "MasterEntity": null, "BaseClass": "Entity", "PageTitle": "Test Three", "MenuIcon": "file-alt", "PrimaryKeyType": "Guid", "PreserveCustomCode": true, "IsMultiTenant": false, "CheckConcurrency": false, "BulkDeleteEnabled": false, "ShouldCreateUserInterface": true, "ShouldCreateBackend": true, "ShouldExportExcel": false, "ShouldAddMigration": true, "ShouldUpdateDatabase": true, "CreateTests": false, "Properties": [ { "Id": "b94be8aa-77fd-452a-a068-c81c06b99883", "Name": "Aaa1", "Type": "string", "EnumType": null, "EnumNamespace": null, "EnumAngularImport": null, "EnumFilePath": null, "DefaultValue": null, "IsNullable": false, "IsRequired": true, "IsFilterable": true, "AllowEmptyStrings": false, "IsTextArea": false, "MinLength": null, "MaxLength": 50, "SortOrder": 0, "SortType": 0, "Regex": null, "EmailValidation": false, "ShowOnList": true, "ShowOnCreateModal": true, "ShowOnEditModal": true, "ReadonlyOnEditModal": false, "EnumValues": null, "IsSelected": true, "MaxFileSize": null, "OrdinalIndex": 0 }, { "Id": "e84ed642-0c97-46db-a4ef-731cf500195d", "Name": "Aaa2", "Type": "int", "EnumType": null, "EnumNamespace": null, "EnumAngularImport": null, "EnumFilePath": null, "DefaultValue": null, "IsNullable": false, "IsRequired": true, "IsFilterable": true, "AllowEmptyStrings": false, "IsTextArea": false, "MinLength": null, "MaxLength": null, "SortOrder": 0, "SortType": 0, "Regex": null, "EmailValidation": false, "ShowOnList": true, "ShowOnCreateModal": true, "ShowOnEditModal": true, "ReadonlyOnEditModal": false, "EnumValues": null, "IsSelected": true, "MaxFileSize": null, "OrdinalIndex": 1 }, { "Id": "f7b3a928-ad23-4ecd-ac6b-d32bdd29795e", "Name": "Aaa3", "Type": "int", "EnumType": null, "EnumNamespace": null, "EnumAngularImport": null, "EnumFilePath": null, "DefaultValue": null, "IsNullable": true, "IsRequired": false, "IsFilterable": true, "AllowEmptyStrings": false, "IsTextArea": false, "MinLength": null, "MaxLength": null, "SortOrder": 0, "SortType": 0, "Regex": null, "EmailValidation": false, "ShowOnList": true, "ShowOnCreateModal": true, "ShowOnEditModal": true, "ReadonlyOnEditModal": false, "EnumValues": null, "IsSelected": true, "MaxFileSize": null, "OrdinalIndex": 2 }... repeat to 130+ fields

..continue. Aaa4-131 as type:int, same type with that: "IsNullable": true, (i have tried combinations of this as well) "IsRequired": false, "IsFilterable": true,

I can send the whole file to email or something... but it's this basic.

a few days ago i did a simple test like yours as well with column names AA1, - AA130.. just to rule-out weird column names or anyting, as well.

All boilerplate code gen from ABP Suite. Literally -- generate, compile, (migrate), run. Nothing particularly special. Which is why i went down the path of confirming the SQL server installation was not in the way and tried another.

I'm executing the query from the app, or from a direct Api URL ( for quick testing) ..

Is the continuous 'invisible' breakpoints a clue? How can we get some additional debug from the depths? I've messed with the settings in Blazor/program.cs which is how i got the addition sql debug from eFCore. Any other suggestions?

Hi, thanks for the suggestion.

Sadly no change, added the decorator to the entity class and/or the base, both.

[DisableAuditing]
public abstract class CurrentOrderBase : Entity<string>

The error is in the query itself for sure .

SELECT COUNT_BIG(*) FROM [app_prodman].[CurrentOrders] AS [c] WHERE [c].[T21_G_AFMONTSP] <= @__t21_G_AFMONTSPMax_Value_0<<<====== should not be here!

There should NOT be a WHERE clause. I think above 128 filter objects being passed the filterarray in the framework is being dirtied somehow and injecting this filter comparison that just shouldn't even be in the Count nor Select logic, then crashes out completely. Remind this is the initial load on the page and as evidenced above when the filter count is below 100 or 120 it works, when above, weird things start happening.

I have also now verified this against SQL EDGE (original) and SQL Server (WINDOWS) .

Same behavior.

hereby also found when stepping through the foreced-breakpoints:

items [List] = Error processing 'variables' request. The operation was canceled.