Sales Pack naming
Collapse
X
-
Looks nice! I can think of a bunch of things to do with that. Worth paying for just for the empathy that went into making it, will give it a test - thanks! -
we also wish to create other Entities with itemList, it seems like a good feature to have available as a Field Type for other Entity designs -
Wondering why you would want to do that name change, since Quote and Sales Order both exist as separate Entities right now, and appear correct in workflow?
My question related to prepending "Sales" to Quote and Invoice for consistency with "Sales Order".
Certainly agree; we also wish to create other Entities with itemList, it seems like a good feature to have available as a Field Type for other Entity designs.
I'm sure I'll have to get dirty with code at some point, but right now it seems much faster to design with the GUI than multi-file work and risk of typo bugs etc. -
It's not possible to rename entity names due to compatibility reasons.Leave a comment:
-
Sales Pack naming
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.Tags: None
Leave a comment: