Backend Logic for new Date Filter Widget #705
Comments
teosarca
added a commit
to metasfresh/metasfresh
that referenced
this issue
Nov 27, 2017
teosarca
added a commit
that referenced
this issue
Nov 27, 2017
teosarca
added a commit
that referenced
this issue
Nov 27, 2017
teosarca
added a commit
to metasfresh/metasfresh
that referenced
this issue
Nov 27, 2017
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Dec 1, 2017
[#2177](#2177) New Window for Attribute Search in WebUI [#3117](#3117) Disable MStorage.add [#1357](metasfresh/metasfresh-webui-frontend-legacy#1357) Don't use the legacy view attributes API [#1367](metasfresh/metasfresh-webui-frontend-legacy#1367) view attributes shall be refreshed when the current selected row is refreshed [#3041](#3041) Forecast Window copy Field content from header to lines when creation [#3040](#3040) Implement Clone/ Copy for Forecast Window WebUI [#1360](metasfresh/metasfresh-webui-frontend-legacy#1360) View field editor: override viewEditorRenderMode on row level [#2868](#2868) Make BOMValidate process to work correctly in webui [#2956](#2956) drop allowconsolidateinvoice from database [#3073](#3073) Error: Could not find or load main class ${argLine} [#3072](#3072) de_metas_purchasecandidate schema containing some diagnosis views [#705](metasfresh/metasfresh-webui-api-legacy#705) Backend Logic for new Date Filter Widget [#3064](#3064) Multiple PP Order generation for a materialdispo line [#3088](#3088) Transform in material receipt left destroyed HU behind [#3086](#3086) HU planned after Purchase Order, destroyed after material receipt [#3089](#3089) Not able to start report service with ReportServiceMain.launch [#3042](#3042) C_Bpartner: new Additional fields [#3060](#3060) TypedSqlQuery Bugs because aggregateList method ignores order [#3054](#3054) purchase candidates: document references me-45
|
IT |
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?
Feature Request
What is the current behavior?
Currently, a date widget for filtering is a date-range widget.
Which are the steps to reproduce?
Open, try and see.
What is the expected or desired behavior?
Create the backend functionality/ configuration possibility to have
How to configure
The text was updated successfully, but these errors were encountered: