Pages

Friday, February 12, 2016

How to delete Salesforce for Outlook database?


When you setup Salesforce for Outlook to a computer, Salesforce for Outlook will create database on local computer. But, for some reasons Salesforce for Outlook sync may error because of the databases corrupted.

To fix the issue, we can delete the Salesforce for Outlook database manually through the steps below:
  1. Close Microsoft Outlook
  2. Close Salesforce for Outlook from tray icon by right click the icon and select Exit
  3. Click Start menu
  4. Type %appdata% and hit enter 
  5. Open Salesforce.com folder 
  6. Open Salesforce for Outlook folder 
  7. Delete DB folder
Open Microsoft Outlook and Salesforce for Outlook again, you need to re-configure Salesforce for Outlook by entering your Salesforce login credential and following Salesforce for Outlook setup screen. Salesforce for Outlook will re-create the database again. But, if you still get error when sync, log a ticket to Salesforce support.



This blog is written with Salesforce for Outlook version 2.9.3 with Microsoft Outlook 2013 on Windows 7 machine.




Wednesday, February 3, 2016

How to Hide Salesforce for Outlook Side Panel in Outlook

When you (Salesforce admin) configure Outlook Configurations in Salesforce setup, there is an option to enable Side Panel. If this setting enabled, users with Salesforce for Outlook installed, user will see a side panel at the right panel of Outlook, this panel will match email address from email open with data in Salesforce.



It's understand that the side panel take some real estate in of your screen, you can simply click >> icon to minimize it.



But, if you want to really hide it, follow below steps:
  1. From Microsoft Outlook, click on the down arrow to show the options for the Quick Access Toolbar
  2. Click on 'More Commands...'
  3. On the Outlook Options window, change the 'Choose commands from' option to 'All Commands'
  4. Scroll down to 'Salesforce Side Panel' and add it, then click OK.



This will create the round icon, and if you click it, you will see the option to easily Show/Hide the Salesforce Side Panel. When it is hidden, it will take less resources, but the agent still active for sync process.


This blog is written with Salesforce for Outlook version 2.9.3 with Microsoft Outlook 2013 on Windows 7 machine.






Thursday, January 21, 2016

Chatter Post visibility


As a Chatter user, have you ever wonder where your post will be visible and by who? Table below explains where your post appears and who can see it.

If you post to...
Who can see it?
Where does it appear?
Why would you post there?
Notes
Your profile
Everyone
- Your profile
- In the Chatter feed of anyone who follows you
Provide general status updates, thoughts, or ideas, share relevant and interesting articles or links
Use your personal feed to share work-related information. People can choose to follow or unfollow you on a whim. They don't receive email notifications for your posts, so there's never a guarantee as to who sees your post.
Coworker’s profile
Everyone
- Your profile
- Your coworker’s profile
- In the Chatter feed of anyone who follows your coworker
Specifically direct a question to that coworker and potentially gain insight from followers
Post to someone’s profile if your followers may not be interested. When you post on their profile, they receive an email notification.
Public Chatter group
Everyone
- The group’s feed
- In the Chatter feed of every group member
- Ask a question, post a file, or share information specifically relevant to that group
- Get feedback and insight from group members
Your broadest and most relevant audience is in topically relevant groups, including people you may not even know. Use groups to ask questions, request feedback, share topical updates, and broadcast important information.
Private Chatter group
Group members only
Unlisted Chatter group
Group members only
Salesforce record (account, opportunity, case, ...)
Anyone with access to that record
- The record’s feed
- In the Chatter feed of anyone who follows the record
- Update information that is specifically relevant to that record
- @Mention a colleague for additional support
- Share a relevant file or link
Rather than emailing a coworker with a question about a Salesforce record, use an @mention on the record's Chatter feed with your question. This takes the work out of contextualizing the email information, and sends an email notification, too. However, the coworker must have permissions to access the object record to see your @mention.


Reference:



Wednesday, January 20, 2016

Salesforce: Getting Started with Fast Update element using Flow

Use case: business users would like easy and fast way to mass update all Opportunity Type to "New Customer" for a specific Account.

Solution: using Flow to mass update all Opportunity Type based on Account Id provided.

1. Create New Flow
Navigate to Setup | Create | Workflow & Approvals | Flows
Click "New Flow" button to start building a flow, you will be bring into Flow Designer.

2. Add Screen "Screen Account Id"
- Name the screen
- Add a textbox field to capture Account Id input by user
- Click green arrow icon to set the screen as Start element

3. Add Fast Lookup "Get All Opty"
- Name the fast lookup element
- Query Opportunity with AccountId equal to screen input field
- Create a sObject Collection Variable, object type = Opportunity, here we name it sobjcollvarOptyToUpdate
- Make sure Id field is save to sObject Collection Variable - we need this for update process


- Connect Screen element box to Fast Lookup box, here is how it looks like at this step:


4. Add Loop element "Iterate Each Opty"
- Name the Loop element
- Loop through sObject Collection variable created
- Create a sObject Variable, object type = Opportunity, here we name it sobjvarLoopOpty
- Assign the collection into sObject Variable


- Connect Fast Lookup box to Loop box, here is how it looks like at this step:


5. Add Assignment element "Set Opty Type"
- Name the Assignment element
- Set Opportunity Type to "New Customer" in sObject Variable


- Connect Loop box to Assignment box, choose "for each value in the collection" in the loop routing option.


Here is how it looks like at this step:


6. Add another Assignment element "Copy to New Collection"
- Name the Assignment element
- Assign sObject Variable (with opportunity Type = New Customer) to a new sObject Collection variable
- Create a new sObject Collection variable, here we name it sobjcollvarOptyFinal
- Select operator = Add


- Connect previous Assignment box to this Assignment box
- Connect this Assignment box to Loop element created earlier, this is to loop next record
Here is how it looks like at this step:



7. Add Fast Update element "Update All Opty"
- Name the Fast Update element
- Use latest sObject Collection variable which contain Opportunity Type = New Customer


- Connect Fast Update box to Loop box, when loop done, the flow will continue to do mass update to all Opportunity.
Here is how it looks like at this step:


8. Add Screen "Success" & "Error"
- Success screen just to show a message that all Opportunities has been updated.



- Add another screen to show error message throw if any error occurred on Fast Update process.


- Connect Fast Update box to Success screen box, continue with drag from Fast Update box to Success screen box, it will automatically show FAULT for the link.



Done, this flow can be enhanced as Process Builder + Auto-launched Flow, example: if an Account is marked as bankrupt, all open Opportunities Stage should be change to Closed Lost.


Reference:



Salesforce: Auto Add User to Chatter Group with Quick Action

In previous blog, we explain step by step on how to configure Process Builder with Auto-launched Flow to auto add user to a Chatter Group upon user creation or re-activation. It's pretty complex as you need to configure a workflow with Time-Dependent Action, continue with Flow, then Process Builder.

There is another option to auto add user to chatter group (not include using apex Trigger), which is using Process Builder with Quick Action, which is much more simpler compare to using time-dependent action workflow and Flow.

Here is the steps:
1. Create Process Builder
2. Select an object
3. Define the Criteria
4. In Immediate Actions, select Quick Actions
5. Enter Action Name
6. Filter Search By Type | Create a Record | NewGroupMember (once selected it will become CollaborationGroup.NewGroupMember)


7. You need to provide 2 variables for the quick actions:
  • Related Record ID = Chatter Group Id
  • Member Id reference to [User].Id




Monday, January 18, 2016

Salesforce: Duplicate Management

More than a year ago, I blogged about using DupeCatcher as duplicate management tool in Salesforce. DupeCatcher was a good tool, but with many new enhancements around Salesforce recently, such as: Salesforce1, Salesforce for Outlook, and Salesforce themselves build something similar as out of the box feature called Duplicate Management (under Data.com setup menu). Also, recent poll in Success - Premier Central, standard Duplicate Management has been used by 45% of community.

After play sometimes with Duplicate Management, I foresee this tool able to replace aging DupeCatcher which has been not updated for quite sometimes. What I like from standard Duplicate Management compare with DupeCatcher:
  1. Work well with Salesforce1 app
  2. Work with Salesforce for Outlook
  3. Better duplicate reporting
  4. Respect duplicate management rules for mass data load

To setup Duplicate Management, navigate to Setup | Data.com Administration | Duplicate Management.

1. Matching Rules
Matching rule compares field values to determine whether a record is similar enough to existing records to be considered a duplicate. For example, a matching rule can specify that if the Email and Phone values of two records match exactly, the records might be duplicates.

Matching rules would be the 1st step you need to setup to configure duplicate management, by default Salesforce provide 3 matching rules for Account, Contact and Lead, but they are inactive. In many cases, you need to create your own matching rules based on how your company / organization defined matching rules. See reference links below to understand standard matching rule for Account, Contact and Lead.

To create your own rules, from Matching Rules page click New button.
  • Step 1. select an object: Account, Contact, Lead or custom object
  • Step 2. enter rule name, description, select fields to compare as matching criteria, you also can add filter logic if it is not always AND. Depend on the selected field type, matching method can be Exact or Fuzzy.
  • Step 3. activate the rule, once the rule activated, you will get email that the matching rule has been activated and ready to use.


2. Duplicate Rules
Duplicate rules work together with matching rules to prevent users from creating duplicate records. A matching rule determines whether the record a user is creating or updating is similar enough to other records to be considered a duplicate, whereas a duplicate rule tells Salesforce what action to take when duplicates are identified. For example, a duplicate rule can block users from saving records that have been identified as possible duplicates, or simply alert users that they may be creating a duplicate, but allow them to save the record anyway.

To create duplicate rules, from Duplicate Rules page click New Rule button and select the same object of Matching Rule created earlier, for this blog I'll be using Account. Next page, you need to specify:
  • Rule Name and Description
  • Select "Record-Level Security", I'll select "Bypass sharing rules" for this blog, this mean matching rule will compare to the whole database regardless user accessibility
  • Action on Create and Edit: allow or block
  • Alert Text
  • Select matching rule created
  • Optionally you can add conditions

Once duplicate rule created, you need to activate it.


When duplicate rule is activated and user enter duplicate data, since we allow user to create or edit with alert, user will get option to Cancel or Save (Ignore Alert), it also shown existing record consider as duplicate with the one user trying to create or edit.


By default, it will show fields used in the matching rules, at this moment we are not able to configure it. Thanks to Francis Pindar for his workaround to have fake matching rule to display fields as needed.


Duplicate Record Reports
As I said earlier, we can report on duplicate record easily, you need to create custom report type by each object (Account, Contact and Lead, or  All Duplicates), read this document Create Custom Report Types for Duplicate Record Reports for the steps.


Reference:


Page-level ad