In campaign, the total value won shows the amount for "closed lost" rather than "closed won" how do I fix this?
The closed won is not reflected by the total value won, but the closed lost reflects the total value won.
Basically I need to know when someone took ownership of a Lead and how many days they've owned it. When it reaches 30 days and the status is still 'Not Contacted" I want to reassign ownership to the Lead Queue.
2. Create a Workflow rule to evaluate the Lead Owner field with an "ISCHANGED" function - if True then the WFrule fires an update to the "Ownership Changed" field to stamp it with TODAY()
3. Create another formula field (Called "Days Since Last Owner Change") that basically calculates "Today - Ownership Changed" (date - date = # of days different).
That will take care of your requirement to see the number of days lapsed since your last owner change. You can then report/filter on that formula field to create interesting exception reports.
What's interesting is that you don't really need all of that to get the ownership to flip back to a queue.
What you need for that is just the "Owner Changed" Date.
You build a Workflow Rule that evaluates this "Owner Changed" Date not being NULL AND Status = Not Contacted. That will fire your rule but - of course you couple it with a Time Based action that will queue the Field Update action (for the Owner Update) 30 days after Rule Trigger.
As long as the criteria that cause this to fire is true the queued action will persist and/or the "fire date" will change if the Lead Ownership changes but the status remains "Not Contacted". Since you set your time based workflow to trigger on "Owner Changed" date that will take care of the corner case of some new rep taking the Lead over and - reseting the clock to 30 more days (as would be expected for a new owner right?).
Keep in mind this all assumes calendar days - not business days. If you want to make this work off of business days you'll need to get fancier.
Hope this helps!
I'm having this issue with one user and I can't get to solve it. She is creating a case within an account and after saving it, the case doesn't appear within the account:
I have to mention that the case owner is NOT the Account owner but she is within the "account team" so she should edit and create records within the account.
After cliking the save button the case it is "created" but it doesn't appear within the account.
If we go to the cases object we can find the cases created but there is no account associated with them:
I will really appreciate your help. I'm new to salesforce and not sure how to handle this.
Thank you so much
I came across an interesting issue with the new ability to deploy a community via change sets that came with the Summer '17 update. I've figured out the resolution as well, which I'll post as an answer to the question, but I wanted to post it here incase it may help others.
I had a Sandbox set up, and created a test community in that sandbox which grew into the actually community we were going to migrate into Production as a brand new community. We hadn't figured out a name for it yet, but by the time it was ready for migration to production we had finalized the name for it and renamed the Community from the placeholder name to the finalized name (we'll come back to why this is important in the answer).
I then followed the steps outlined here and created a brand new community in Production with the finalized name we had decided on: https://releasenotes.docs.salesforce.com/en-us/summer17/release-notes/rn_networks_changesets.htm
Then I made an outbound changeset in the sandbox, selected the Network object for the community and then added the two Site.com dependancies.
I uploaded the changeset to production, and then when I went to deploy the changeset I recieved the following error:
"An unknown exception has occured."
Not super useful, and searching Salesforce success, help, and googling in general yeilded no results, which made sense since this is such a new feature.
So what could be causing this error?
- If you rename a Community to it's final name in the sandbox but the Community you created in Production the final name from it's creation point.
- If you have the correct final name for the Community in the sandbox right from it's creation point, but perhaps when creating the Production Community, you mistyped the name so then you go ahead and rename it to match.
Let's say for example you have a Community named "Temp Community Name".
When you make a changeset for a Community and add the Network component you'll see the APIName "Temp_Community_Name", and then when you add the dependancies you'll see 2 Site.com components with APINames "Temp_Community_Name" and "Temp_Community_Name1" respectively.
If you go and rename that Community to "Final Community Name" and make a change set and add the dependancies you'll get a Network with the APIName "Final_Community_Name" and 2 Site.com components with APINames of "Final_Community_Name" and "Final_Community_Name_C"
So when renaming a Community, the APIName of the 2nd Site.com component changes the "1" at the end to "_C".
Then if you create a brand new Community in Production and name it "Final Community Name", in the backend it's APIName is "Final_Community_Name1", so when you try and deploy the changeset from the Sandbox to Production, it gives you the unknown exception error because it's trying to match up the Site.com component "Final_Community_Name_C" from the Sandbox into "Final_Community_Name1" in Production and fails.
The reverse of this is true as well, as stated above, if you never rename the Community in the sandbox, so it has "1" at the end, but for some reason you have renamed the Community in Production so that it will match the name in Sandbox, it will now have "_C" at the end and the same failure will occure.
The solution to this is that if you see "_C" in your changeset for that second Site.com component that means you've renamed your Community at somepoint, so go and rename your Production Community to something else, and then rename it back so that it still matches your Sandbox Community. This will change the APIName of the Production second Site.com component to have the "_C" so that it will now match what is in your Sandbox and you will be able to deploy successfully!
In the calendar you see both the tasks and events? I know in the Lightning Home page you can see just today's tasks and events. So the only way to see the week or month events and tasks is going to the Calendar object?
Name, Last Name, Company, Email, Domain, and Phone.
You can look for an appexchange app for this.
I've created a Custom Object called Apps and I have a Lookup field linked to Opportunity to select Opportunity. Name.
I now want a second field that will be populated with Opportunity.Fabricator field based on the Opportunity I select. From looking at other objects in my Org, I'm using a Formula field to do this - basically the formula is Opportunity.Fabricator but the syntax failed based on Opportunity field not recognised.
Where am I going wrong or how can I achieve this ?
Thanks in advance,
Can anyone please explain to me as to what is the difference between Salesforce lightning and Salesforce1 App, or how are they related?
Salesforce.com Introduces Salesforce1. Salesforce1 is the new social, mobile and cloud customer platform built to transform sales, service and marketing apps.Salesforce1 is the first CRM platform for developers, ISVs, end users, admins and customers moving to the new social, mobile and connected cloud. Salesforce1 is a brand new app which replaced Salesforce Chatter and is what most of the current Salesforce buzz surrounds. In theory it'll allow you to make use of ALL Salesforce functionalities from your mobile, including all custom objects, apps and even Visualforce pages. It's also feed-first, so Chatter is central to it.
Lightning Experience, the new, fast, beautiful user experience from Salesforce. With a sales-centric mindset, we focused on reinventing the desktop environment to better support your sales process. The result is an intuitive, intelligent interface that helps sales reps work more naturally and close more deals faster.
It’s really just the beginning! Lightning Experience will transform Salesforce CRM and extend to service, apps, platform, and more. No matter what department you're in, we understand that the way people work is changing.
All this change is greatly influenced by the rise of mobile. Sales reps at your company are already using mobile to research prospective customers, get directions to client meetings, connect socially with customers, and more. We get that. That’s why Lightning Experience takes the cool stuff from the mobile experience and brings it to the desktop.
Salesforce1 is using same framework for user interface like lightning but both are dieffrent.
I can mass edit certain fields in a list view HOWEVER, if I have any filter logic in that list view, I can no longer edit the fields.
Anyone have a work around for this?
Inline editing from a list will not work if there are any "OR" filters in conjunction with a record type filter (all list filters must be joined by an "AND" logic).Take a look here (https://help.salesforce.com/articleView?id=000003911&type=1)
I do not know nor write triggers.. Several were written before I came on as the Admin.
I have a Trigger that is designed to change the record type on Accounts after our daily bulk import.
I have recently gotten several "fails" and was hoping someone could tell me why.
And is there an easier way (workflow) to write this than a trigger?
My fail is at Row 28 / Column 1
Hey Kim -
When you do an upsert, the match will be done on the Salesforce record ID or a custom field marked as an 'external Id'.
From the Process perspective, it won't matter which record since the Process will be looking at whatever record gets created or changed and then seeing if that meets the criteria.
A suggestion: before you start actually changing anything, make sure you map out each piece of the current solution, what it does, and how it passes data to the next piece. Then, map out what you plan to build and make sure the "what it does" and "how it passes" match. Also, it can't hurt to build this in a sandbox and test it with a few records.