Thoughts on where to put this? Should we create a custom user field for each month?
3 réponses
Hi Amber,
The problem with using mutiple fields on the User object for each month and then comparing them to 1 Field on the Case object over a period of time is that you won't be able to compare them side-by-side.
I built something a while back to compare Users Sales vs Goal using custom Record Types and Page Layouts. Essentially I created 2 Opportunity Record Types (Sales and Quota).
With a few tweaks you could do the same thing with Cases, create Budget Cases and assign them to Users and then using stanbdard Case Reports compare Users Cases vs Budget side-by-side.
Here's quick snapshot of what I built and how it works in a Nutshell
Object = (Standard) Opportunity
Record Types = 2 (Sales and Quota)
Page Layouts = 2 (Sales and Quota)
Sales Processes = 2 (Sales and Quota)
Quota Sales Process has only 1 Stage set to (Closed/Lost, 0%, Omitted) so there's no way it will accidentally fudge Revenue, Expected Revenue, Forecasts, etc. even if someone forgets to exclude if from a Report.
Quota Page Layout is stripped down to the bare bones, even Account Name is optional. Allowing Exec level to assign a "Raw $ Number Target" to a SalesRep or Team that is not tied to an Account or Product. In other words they can say "Your 2014 target is $1M I don't care what you sell or who you sell it to, that's your number" and you can run a Sales vs Quota by SalesRep/Team and compare Sales vs Goal.
Using RecType and Page Layout you can control/assign who can create, edit, view Quota Opptys using native SFDC Admin/Profile settings.
I also created a couple of custom Formula fields for Reports so you can do stuff like Variance Report (Sales Amount - Quota Amount) and stuff like that.
Anyway, it's just an idea that I came up with. I like Leonardo DaVinci "my mind is full of ideas", and most of them are as useless as a Wooden Helicopter powered by ropes and pulleys.
