Here is what I am trying to accomplish:
1) If Closed Lost Reason is PICKVAL 'Other'
2) Then Text(250) Field Other Reason CANNOT be Blank
Here is what I did and it is not work :(
ISPICKVAL( Loss_Reason__c ,'Other'),ISBLANK('Other_Loss_Reason__c'))
*Not sure if this matter but there is a field dependency on Stage = Closed Lost
*Also we use 3 record types.
The validation rule would like this:
AND( ISPICKVAL(your_picklist_field_api_name, "Yes"), ISBLANK(your_text_field_api_name) )
It will force them to fill that field out but It won't cause a pop up to appear. You can define a visual flow to handle that functionality.
I need to get the email address from my Lead records transfered to the Opportunities records that are created when Leads are converted. This will allow me to automatically email the Lead/Contact based on changes in the Sales Stage.
I've tried to accomplish this via Lead Conversion Field Mapping and Process Builder (process triggered by Opportunity creation) but having trouble.
Lead Conversion Mapping Efforts:
(1) I made a custom Lead Field "email copy" that copies the Lead Email field using a text forumla. The problem with this is that it seems I can only map the "email copy" field to other custom fields of the type "text." I need this mapped to an "email" not "text" type field.
(2) I tried making a custom Lead Field "email copy 2" that used a formula to copy the email field value but was told "Error: Field email may not be used in this type of formula"
Process Builder Efforts:
Upon Account creation, I'm trying to copy the Contact Email to the Account record and then copy the email from the Account record to the Opportunity Record.
But I can't even get the first part (copy email from Contact to Account) accomplished.
I have a custom "Email" field field on accounts. I try to update this field using a field reference but I cannot reference the related contact. The closest thing I can find to Contact is Primary Contact. But Primary Contact has not been set.
So I try to first set Primary Contact using a reference to the Contact record but, again, I cannot find the Contact record as a field I can reference.
How do I get my Lead Email on the Opportunity Record???
Was the lead conversion process specifically designed to prevent any interesting or useful sales automation from happening?!? It sure seems so...
Welcome to Salesforce, where we are very fond of our ancient tradition of not allowing you to map a standard Lead field to a custom Account, Contact, or Opportunity field on conversion. That is how our fathers and grandfathers lived, and that is exactly how we are going to raise our children.
What we will allow you to do is to create a custom email field (not a formula - that won't work) on the Lead and a Workflow Rule and Field Update that inserts the value of the standard email field into the custom field. Then map the (non-formula) custom Lead field to the custom Opportunity (or Account) field.
'tis the proud and true way of the Salesforce.
We are working on a single org structure for our Sales Cloud solution. Our sales reps are distributed in various braqnches across EMEA including Russia.
We are about to start our implementation for our Russian branch and have some doubts regarding Russian Data Security Laws
We were informed by our team in Russia that in order to comply with the Data Protection regulations, we would need to use an application (or plug-in) called DFG152. It seems this app helps in storing the data in a local data centre, encrypting the personal data in Russia and then storing it in Salesforce Cloud
Can anyone please guide us with how this works and shed some light on DFG152. We dont have a very good idea of what this is
Thanks in advance!
That article article is to show you how to grant Pardot permission to use custom fonts through an Apache configuration change, as some browsers may block custom fonts like Firefox and newer versions of Internet Explorer block access to custom fonts that are requested from third-party domains
You can find help for setting up custom fonts on other webservers here: https://enable-cors.org/server.html
Hope this helps,
Go to Your Name » Setup » Develop » Pages
Copy/paste the following code into a new Page replacing what appears by default. Notice that in this example we're using custom fields for the Account address components:
Is there any way that I can prevent creation of opportunities that aren't created through a contact or a converted lead?
Setup > Customize > Home > Homepage Layouts, edit the one you're interested in, then remove the checkmark next to 'Create New'.
Then add a customs section with links to create the records they are allowed to.