Using LifeCycleStage Values for Calculated Properties
resolver
Hi, I'm creating a Calculated Property called "Customer/Lead", which I want to be a formula like this one:
If ((LifeCycleStage == "Customer"), "Customer", "Lead")
Basically what I'm trying to do is to use that field to build a report of the different companies that are in my Deals Main Pipeline, and report the amount for Customers, and the Amount for every other type of Company.
The problem I'm facing is that I don't know what is the internal value for the Customer Value and how to put that in the formula.
When I treat it like a String, and use the value that the Property Settings show me as the "internal name", I don't get a good result. Everything goes to the "else" side of the formula.
So, I'm asking for some help. Do you know how to write this formula and ask for the "Customer" value?
Using LifeCycleStage Values for Calculated Properties
resolver
@MMazurski in my experience with the tool then, what you're looking to do isn't an easy standard fix. It sounds more like a process discussion (using the properties that exist in their intended manner) than a technology one (creating custom calculated properties), but others may have a different tip for you with custom coding in calculated properties. Thanks for the clarification, and all the best on finding the solution that fits your needs. I hope someone has an answer that helps!
Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!
Using LifeCycleStage Values for Calculated Properties
resolver
@MMazurski instead of something custom and calculated, could you use the Company property "lead status" or "status" or maybe the Deal property "Deal type" and filter by something like "new business" or "existing business"? I'm not sure I totally understand why it would need to be a calculated property if I get what you're doing, which I think is reporting on new business vs. repeat (usell or cross-sell) business.
Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!
Using LifeCycleStage Values for Calculated Properties
resolver
Thanks for the response. A report is what I want to do. If I use the Deal Type or any other property, I would need to put efforts in updating those properties manually, and most of the time we don't use them.
The report shows Corporate the revenue and number of deals that are in the pipeline for Leads and Customers, grouped by these 2 categories.
So my idea es to create a calculated field with a Formula like this one:
Using LifeCycleStage Values for Calculated Properties
resolver
Instead of focusing on internal value, could you build a report with the Custom Report Builder (multiple objects) where you include Deals as the primary data source and Companies as a secondary data source.
Then in your bar chart you could pull in Amount (in company currency) [Deal], Lifecycle Stage [Company], and Deal Stage [Deal].
This would then show you how much revenue is in each stage (bar chart) while each column could be broken down by the companies lifecycle stage.
Using LifeCycleStage Values for Calculated Properties
resolver
@MMazurski in my experience with the tool then, what you're looking to do isn't an easy standard fix. It sounds more like a process discussion (using the properties that exist in their intended manner) than a technology one (creating custom calculated properties), but others may have a different tip for you with custom coding in calculated properties. Thanks for the clarification, and all the best on finding the solution that fits your needs. I hope someone has an answer that helps!
Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!
Using LifeCycleStage Values for Calculated Properties
resolver
Thanks, Dan. I like that my question isn't a dumb one to start with. I totally get what you are saying, and if I don't find an automated solution that prevents my team from filling 1 more field, I'll take the "change the process and put a little more overhead" way.
First, for information, I'd like to share this article "Create calculation properties" that might be of interest to you.
I also wanted to invite a couple of subject matter experts to this conversation @Josh, @danmoyle and @louischausse, do you know of a workaround or a formula for this to help @MMazurski, please?
Also, if anybody else has anything to add and/or share, please feel free to join in the conversation 🙂