Created as a maintenance task based on discussion between @timschofield and @pakricard in "New HR system" #894.
I agree with the premise and believe webERP could only benefit from the simplification (assuming the work is not left "good enough for now" but someone sees it through all the way to the end). The master contract record can simply be the compilation of all the needs of all modules (one level of refactoring or pre-optimisation could be tolerated if the future gain would be significant).
There may be a "best way" for third-party code to extend the master contract information for the own purposes, but it is not the concern of webERP beyond speculating that such a method does exist (webERP's concern is only that all webERP code uses and only uses the master contact record).
@pakricard : I think it would be a massive code improvement to compile all addresses in webERP in a table (suppliers, customers, shipments, etc). I guess that was the idea behind addressbookid but it is a wide system change and we should tackle it independently in another discussion and time.
@timschofield It still is in my mind to do. It's probably a mistake to allow that field through for now though
Created as a maintenance task based on discussion between @timschofield and @pakricard in "New HR system" #894.
I agree with the premise and believe webERP could only benefit from the simplification (assuming the work is not left "good enough for now" but someone sees it through all the way to the end). The master contract record can simply be the compilation of all the needs of all modules (one level of refactoring or pre-optimisation could be tolerated if the future gain would be significant).
There may be a "best way" for third-party code to extend the master contract information for the own purposes, but it is not the concern of webERP beyond speculating that such a method does exist (webERP's concern is only that all webERP code uses and only uses the master contact record).
@pakricard : I think it would be a massive code improvement to compile all addresses in webERP in a table (suppliers, customers, shipments, etc). I guess that was the idea behind addressbookid but it is a wide system change and we should tackle it independently in another discussion and time.
@timschofield It still is in my mind to do. It's probably a mistake to allow that field through for now though