Great work on the Sales Pack.
I need to implement a clone of this for purchasing, so will need to distinguish between Sales & Purchases.
My suggestion being that Quote is renamed Sales Quote and Invoice is renamed Sales Invoice.
I realise this may seem like a minor thing that can be handled with the Language/Label aspect, although perhaps you'll also appreciate a self-explanatory database naming in this context.
Since what I'm working on will be cloning the Sales Pack and repurposing for Purchases, so Purchase Quote, Purchase Order, Purchase Invoice, I thought you might consider the same so we retain compatibility with your updates as opposed to forking that pack.
Sorry, I'm sure my detail questions are an overhead, although hopefully you can see my commitment to the platform and future-proof data design.
I need to implement a clone of this for purchasing, so will need to distinguish between Sales & Purchases.
My suggestion being that Quote is renamed Sales Quote and Invoice is renamed Sales Invoice.
I realise this may seem like a minor thing that can be handled with the Language/Label aspect, although perhaps you'll also appreciate a self-explanatory database naming in this context.
Since what I'm working on will be cloning the Sales Pack and repurposing for Purchases, so Purchase Quote, Purchase Order, Purchase Invoice, I thought you might consider the same so we retain compatibility with your updates as opposed to forking that pack.
Sorry, I'm sure my detail questions are an overhead, although hopefully you can see my commitment to the platform and future-proof data design.
Comment