-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lookup validation rule shall support @CtxName/Default@ annotation #585
Comments
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Sep 14, 2017
* IExpression: rename getParameters() to getParamertsAsPlainStrings and added a new method getParameters() that returns CtxNames. CtxNames are more useful because they can contain a default value, but they can also contain a "normal" string. In our case, we need CtxNames so we can evaluate the @CtxVar/Default@ notation that is contained in many of the expressions we deal with. * CtxNames: add new static utility class around CtxNames to separate the static code from the actual instance code. * Implement the new CtxName returning getParameters() method wherever needed; in most cases that means returning the CtxNames that are already embedded in the respective implementations. Lookup validation rule shall support @CtxName/Default@ annotation metasfresh/metasfresh-webui-api-legacy#585
metas-ts
added a commit
that referenced
this issue
Sep 14, 2017
..mostly in LookupDataSourceContext Also * adapt to the API changes made in metasfresh * do a bit of cleanup Lookup validation rule shall support @CtxName/Default@ annotation #585
This was referenced Sep 14, 2017
Merged
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Sep 14, 2017
Lookup validation rule shall support @CtxName/Default@ annotation metasfresh/metasfresh-webui-api-legacy#585
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Sep 14, 2017
Also renamed other stuff thx @teosarca Lookup validation rule shall support @CtxName/Default@ annotation metasfresh/metasfresh-webui-api-legacy#585
metas-ts
added a commit
that referenced
this issue
Sep 14, 2017
Also renamed other stuff in metasfresh Lookup validation rule shall support @CtxName/Default@ annotation #585
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Sep 14, 2017
Lookup validation rule shall support @CtxName/Default@ annotation metasfresh/metasfresh-webui-api-legacy#585
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Sep 14, 2017
Thx @teosarca, for the hint Also simplify the CtxNames.parse method Lookup validation rule shall support @CtxName/Default@ annotation metasfresh/metasfresh-webui-api-legacy#585
metas-ts
added a commit
that referenced
this issue
Sep 14, 2017
Lookup validation rule shall support @CtxName/Default@ annotation #585
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Sep 14, 2017
Lookup validation rule shall support @CtxName/Default@ annotation metasfresh/metasfresh-webui-api-legacy#585
metas-ts
added a commit
that referenced
this issue
Sep 14, 2017
Lookup validation rule shall support @CtxName/Default@ annotation #585
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Sep 15, 2017
[#2218](#2218) User would like to import default values for contact and address [#2245](#2445) Support quantity in flatrate term import [#2361](#2361) Invoice Candidates Action Approval for Invoicing [#2387](#2387) Autocomplete for zip / postal code and city [#2298](#2298) Introduce source-HU to fine-Picking [#2247](#2474) Extend Partner Import with ad_language [#585](metasfresh/metasfresh-webui-api-legacy#585) Lookup validation rule shall support @CtxName/Default@ annotation [#2459](#2459) shipto and billto contact / user [#2436](#2436) Use default values for IsShipTo and isBillTo when importing bpartner [#2457](#2457) Duplicate locations on partner import when multiple contacts [#2463](#2463) Extend Partner Import to support contact flags [#142](metasfresh/metasfresh-webui-api-legacy#142) Provide v11 / CAMT 54 File Import [#2429](#2429) hide qty TU when HU name is empty [#2423](#2423) fix jaspers for vendor return with quality issue [#2430](#2430) Invoice candidate close is retrieving the invoice candidates out of transaction [#547](metasfresh/metasfresh-webui-api-legacy#547) Provide mass export of Data to Excel [#570](metasfresh/metasfresh-webui-api-legacy#570) clicking print on non-document window shows error page [#2431](#2431) Product Filter in Handling Unit Editor [#2413](#2413) Make request status a search field in request window [metasfresh/metasfresh-parent-legacy#14](metasfresh/metasfresh-parent-legacy#14) Look for a way of not having the "placeholder" on local builds [#178](metasfresh/metasfresh-webui-api-legacy#178) Have Letter Feature in Sales Order Window [#2401](#2401) vendor return with quality discount [#2434](#2434) Make field ad_user_incharge_id from C_Flatrate_Term optional [#2397](#2397) Import and Store Contract meta-data e.g. startdate on flatrate [#2412](#2412) OrderCheckout Jaspers display empty C_BPartner_Product.ProductName [#582](metasfresh/metasfresh-webui-api-legacy#582) Cannot invoice disposal's invoice candidates [#1060](metasfresh/metasfresh-webui-frontend-legacy#1060) Locale viewing and editing in User Interface [#583](metasfresh/metasfresh-webui-api-legacy#583) Provide the document's standard actions [#581](metasfresh/metasfresh-webui-api-legacy#581) API to provide user session's locale me-45
checked with metas-ts: can be moved to Done |
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?
See issue metasfresh/metasfresh#2440: The lookup for
M_QualityInsp_LagerKonf_Version_ID
does not return anything, because it's use has... @ValidFrom/0001-01-01@...
in it.Which are the steps to reproduce?
Try creating a new material tracking record
What is the expected or desired behavior?
the validation rul should be evaluated the same way it happens in the old swing client.
The text was updated successfully, but these errors were encountered: