Comments
Hello MS,
is there any update on the idea? As it was planned in the last year, is there a plan to include it in the new release? Also at least the field "Merged" could be searchable to include in the detection duplicate rules to avoid already seeing the inactive records that were already merged.
Thank you in advance for any update.
My controller brought this up to our attention today and I would like to understand the intended behavior.
If I create a new Purchase Invoice for a vendor which I receive Oct 3rd but is dated Sept 26th, I would like to date the document date of Sept 26 and the posting date of Oct 3rd.
We added an EventSubscriber on the OnAfterInitRecord so that the Document Date would not default to Today() / WorkDate() but if the user enters the Sept 26th date in the document date, and Oct 3rd in the Posting date, the validation event on the posting date field updates the Document Date to the same value as the posting date.
This is not accurate now as my due date is based off of the Document date + Terms Code setting for that vendor.
If somebody can help me understand this that would be great...
Thanks
Adding some more scenarios to the idea:
After working with multiple customers in various industries (pharmaceutical & chemistry), all of them required a setup matrix to accurately plan their productions. This led to redeveloping same solution for each customer individually with all its negative implications towards updates etc. Nearly all customer were irritated NOT having this essential functionality as production module all in all is excellent.
An integrated setup matrix would reduce implementation costs, reduce interfaces to planning systems used for matrix planning and raise standard percentage.