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
Allow configuring lookup cache reset on table record changes #954
Comments
teosarca
added a commit
to metasfresh/metasfresh
that referenced
this issue
Apr 28, 2018
also, * introduced AD_Val_Rule_Dep table * a bit of cleanup/refactoring: introduced more default methods to IValidationRule metasfresh/metasfresh-webui-api-legacy#954
teosarca
added a commit
that referenced
this issue
Apr 28, 2018
note to IT:
|
metas-ts
added a commit
that referenced
this issue
May 4, 2018
#954-api - Allow configuring lookup cache reset on table record changes
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
May 7, 2018
[#3989](#3989) pharma: repack number attributes [#3977](#3977) Pharma: Prices from IFA import are in cents [#954](metasfresh/metasfresh-webui-api-legacy#954) Allow configuring lookup cache reset on table record changes [#3982](#3982) Pharma vertical for Discount Schema Window [#2558](#2558) All existing configs available in Gebindekonfiguration in PP_Order [#952](metasfresh/metasfresh-webui-api-legacy#952) Shorten the ViewIds [#3969](#3969) Pharma: If Shipment Auth Type B then show in Order Header [#959](metasfresh/metasfresh-webui-api-legacy#959) NPE when opening Manufacturing Issue/Receipt [#3916](#3916) QtyPicked not updated in shipment schedule after reactivate & unpick in picking terminal [#3984](#3984) Invoice candidate for canceled term and reactivated sales order keeps invalidating itself [#3926](#3926) Implement support for `der Kurier` shipper
IT OK |
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?
At the moment there is no way to invalidate the lookup's cache when a record on which that lookup is depending was changed.
Which are the steps to reproduce?
What is the expected or desired behavior?
Have a way to specify on which tables a given validation rule is depending.
When a record from that table is changed all lookups which are using that validation rule will be cache invalidated.
The text was updated successfully, but these errors were encountered: