A third field needs the following to happen. It should equal the Opportunity amount roll up field if the adjusted field is blank. If the adjusted field is not blank then this should be the amount in the field.
This is my formula:
(ISBLANK( Adjusted_MRR__c )),
When the Adjusted_MRR__c is blank my field comes up $ 0.00 instead of the Closed_Won_Opportunity_s__c amount. But When the Adjusted_MRR__C is not blank then this amount shows up.
Why is my Closed_Won_Opportunity_s__c amount not showing up??
I wanted to create a Validation Rule that when the Stage = Closed Won & Product Type = OCP Development Suite the Product Duration CANT be picklist value - N/A It Must be picklist value = 9 Months or 12 Months.
I tried this but it didnt work, Any ideas;
AND( ISPICKVAL(StageName,"6 - Closed Won"),
ISPICKVAL(Product_type__c,"OCP Development Suite"),
If you were to do that, all you would need to do is:
AND( ISPICKVAL(StageName,"6 - Closed Won"), OR( ISPICKVAL(Product_type__c,"OCP Development Suite"), ISPICKVAL(Product_type__c,"MDP Y1"), ISPICKVAL(Product_type__c,"MDP Y2") ), ISPICKVAL (Product_Duration__c,"N/A"))
That should do the trick! I'm glad it worked Chris, if you can, can you mark the best answer, that way it can help others who might have this same question in the future!
I currently have a process that will write the quote grand total to the opportunity amount field. using this process to eliminate the need to sync the quote. We have another custom field "extended price" - when a number is in amount field it writes to this field. however, when an order is created in our ERP system, "extended price" updates, amount does not. how can I add to my process to basically say:
"if extended price field is not equal to amount field, copy extended price data to amount field"?
So far, I had just one type of users in SF and now I'm going to create users for two other countries. That is why I wanted to ask about best practises. At least 80% of e.g.account layout(fields) will be the same, however some of the fields will be country-specific.
1. Is it better to use separate layouts? Or the same layout but to make fields visible depending on the user role?
2.Any difficulties I can encounter? If I have multiple of layouts as an admin, do I have to each time assign different layout for myself to work with different countries or can I somehow avoid this drawback?
Thanks for your help :) I don't want to end up in the future with several layouts if this is going to be an issue somehow.
Page layouts are tempting at first, but in the long run they'll give you many headaches. I know because I've gone down that route before, only to regret it months later.
Field-level security is a better solutions for a few reasons:
1. You're going to have to control field level security no matter which option you choose. Reps will still see the fields outside of layouts, and you don't want to bombard them with options for example when they are running reports. This will hurt your adoption and usability in the long run, especially after you have many country-specific fields.
2. You might legitimately need to use page layouts for other business purposes in the future, for example, on Opportunities you might have a different record type and layout for a new but separate business process. If you're going with different page layouts for each country, this requirement could multiply your page layouts twofold!
3. When you create new fields, you're going to have to go to each layout individually and manually adjust the position of your new field on each layout. Extremely frustrating!
The most important thing to remember about page layouts is that they are just one way of accessing/modifying records, so you don't want to have too much depending on them. An analyst could still modify a field through Data Loader for example, even though they can't see the field on any layout. Using page layouts as a method of security is the same as locking your front door but leaving all your windows and side doors open!
Hope this help Paulina, and if you like it, feel free to give this a good rating!
Whenever an account is created
'Completed Questionnaire' = 'FALSE'
For some reason, all of my clients are currently receiving the reminder emails, even those that have the 'Completed Questionnaire' field changed to 'True' which I thought would remove them from time based flow.
I have posted some screenshots of my process. Please let me know if I have built this out wrong, I can't see any obvious issues with it.
Just to be clear the problem is that records are not being removed from the time based workflow even when the record changes during the time interval such that it should no longer qualify.
Here is the full process. The filters are set appropriately to get people down the right channel, but for some people are not being removed from the time based workflow when they no longer fit the criteria.
Let me know if more info is needed.
I figured it out. I was not aware that Process Builder does not re-evaluate processes when there is field changes UNLESS you set the process to trigger 'when a record is created or edited' and in the criteria settings you select 'Yes' where it asks 'Do you want to execute the actions only when specified changes are made to the record?'. So for time based workflows built in the process builder, you must choose these settings.
Here is a little documentation excerpt:
"For processes that are set to run when a record is created or edited, scheduled actions remain in the queue only as long as the criteria for those actions are still valid. If a record no longer matches the criteria, Salesforce removes the scheduled actions for that record from the queue."
"For processes that are set to run when a record is created, Salesforce never reevaluates the record with that process. Scheduled actions remain in the queue, even if the record no longer meets the associated criteria when the scheduled actions are executed."
I'll leave this here for anyone grappling with the same issue.
Please let me know if you need more information or additiona screen shots.
Now that I think about it, the currency field is a formula with Currency as the output. It pulls the value of the Amount field and if marked as one time revenue on the Opportunity, dividies the amount by 12. Otherwise it displays the number in the Amount field. Perhaps that is my issue?