Coming from other Cloud ERP and CRM systems, I am crazy about best practices on customisations, especially in light of a) system performance, b) reporting capabilities, and c) compatibly with other customisations and new releases (in order of priority).
To that end, I wanted to ask whether there is any guidance on database design when creating custom fields, in terms of those a,b,c outlined above.
Do you have a golden rule when to go for NameValuePairs (effectively an enumerator table, isn't it) and when perhaps even creating a custom table manually in advance?
Our the other way round, is there ever a good reason to add string fields straight to the standard tables.
Is there an efficient way to validate performance impact (across the deployments) and has anyone tried tracking it?