Max rows loaded in a included tab shall be configurable #1119
Comments
teosarca
added a commit
to metasfresh/metasfresh
that referenced
this issue
Jan 7, 2019
teosarca
added a commit
that referenced
this issue
Jan 7, 2019
metas-ts
pushed a commit
to metasfresh/metasfresh
that referenced
this issue
Jan 7, 2019
…ax.sql metasfresh/metasfresh-webui-api-legacy#1119 (cherry picked from commit cbc47b7)
|
🍒 picked #1119 to |
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Jan 14, 2019
* [#4798](#4798) AD_RefList Description shall be shown in webui * [#4863](#4863) Add created/ updated to asynch workpackage and filter for created * [#4857](#4857) Add PK column AD_OrgInfo_ID * [#1119](metasfresh/metasfresh-webui-api-legacy#1119) Max rows loaded in a included tab shall be configurable * [#4862](#4862) When deleting a AD_Tab, the AD_Field and AD_Element_Link records shall be deleted * [#2120](metasfresh/metasfresh-webui-frontend-legacy#2120) Tab not always working correctly * [#2135](metasfresh/metasfresh-webui-frontend-legacy#2135) sync all contract specs - add contracted vendor and discount schema
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a bug or feature request?
FR
What is the current behavior?
Atm, the system logs a warning a 100 rows and loads maxium 300 rows.
Which are the steps to reproduce?
open a document which have more then 300rows in one of it's subtabs.
What is the expected or desired behavior?
Those limits shall be configurable via sysconfig.
The text was updated successfully, but these errors were encountered: