How can Salesforce help you? Salesforce is a household name in the world of Customer Relationship Management (CRM) tools.  It’s been around for 15 years, has (literally) millions of users and boasts a robust suite of features.  Like with any household name product, it’s natural to wonder if the hype is deserved.  Does it actually help you, the Account Executive, do a better job? At its most basic, Salesforce is an excellent tool for managing information about prospects and customers.  This is a fundamental function of all CRMs but Salesforce does it particularly well.  When you consistently log information about your contacts in Salesforce, it becomes a real-time account of each relationship — when it began, the first email you ever sent them, what you discussed during your phone call on March 3 and whether they attended that lunch-and-learn you invited them to last month.  It’s a 360-degree view, without a paper file folder.  Aside from improved organization, why does managing all of those details matter?  

It creates a library of data that Salesforce can then pull summaries, reports and analytics from.  You can create and customize dashboards, graphs and views that show you, for example, opportunities won and lost, how much time has been spent with a specific customer and what the results have been, and what the selling trends are.  This provides incredible opportunities to tailor your efforts and create strategies based on real data — not assumptions. What these powerful records and data sets lead to is better, more personal relationships with your customers. Because Salesforce can help you adapt your strategies to better suit individual contacts, your interactions with prospects and customers will become more natural and instinctive. Customer satisfaction will improve, as well as loyalty, and in the end, your reputation as a winning salesperson. The short URL of the present article is: http://wp.me/p4Rc7e-gmSalesforce Tailors Platform for the Financial Services Industry with Financial Services Cloud

Tuesday, 12 July 2016 In April 2016, Salesforce introduced its first industry-wide product, the Financial Services Cloud (FSC). Built on customer relationship best practices, FSC is a solution that addresses the system needs of the Financial Services industry out of the box and can be customized further to meet the needs of individual companies. There are so many new features in the Financial Services Cloud that I unfortunately can’t cover all of them, so I am going to highlight just a few in this week’s post. One major change with this rollout is the removal of the concept of Person Accounts. Prior to the creation of the Financial Services Cloud was the Wealth Management template, which utilized Person Accounts. Because FSC does not include Person Accounts, it can support both B2B and B2C companies while avoiding some of the limitations that are associated with enabling Person Accounts. Instead of Person Accounts, FSC utilizes the concept of Households and Clients.

The Client tab aggregates information about the Client from other areas in Salesforce and shows related information to the Client. One feature that I really like, is how you can access subtabs directly from the Client tab. This makes is easier to view and organize Client data. For example, from the Client tab you can view the following subtabs: Client Details (this is where you can find standard contact information or any custom information regarding the Client that you would like to track)White Full Length Mirror Target Financial Summary (which can show related information regarding Financial Accounts, Insurance Policies, and Assets or Liabilities)Most Filling Weight Loss Shake Relationships (which provides a summary of the Client’s Household as well as Related Contacts which are anyone else who influences the household)Matching Laminate Wood Flooring

Goals (perfect for capturing and tracking information related to the Client’s desires to better advise the Client) Related (where you can find Opportunities associated to the Client) Reporting and Dashboards (out of the box reporting that has been customized to Financial Service’s needs, such as the My Book of Business dashboard) FSC also takes advantage of the new Lightning Experience interface, so it is built with some of the latest Salesforce features in mind. For example, it utilizes the new home page layout for Lightning Experience and has included a new feature called Assistant. The Assistant will proactively remind you of activities that may need attention or follow-up. These are just a few of the exciting new features that have helped to transform Salesforce from a traditional CRM solution to a more tailored platform geared to the Financial Services industry. As a Salesforce certified partner, EMS Consulting is well versed in FSC and excited to work Customers who are new to Salesforce or the Financial Services Cloud.

If you are interested in learning more about the Financial Services Cloud or have questions about anything Salesforce, reach out today. Why not get your questions answered by the experts? EMS Consulting Launches New WebsiteType Ctrl/C in the command window running the application, and wait for it to shut down.Specifically, you will find a line that looks like This line says that Over the Edge should use Salesforce’s production org endpoint for SOAP services. If you wish to use the sandbox org endpoint, replace this line with *Any files not listed in the above table are for application internal use and should not be touched.* Constituents: Mapped to Contacts and Accounts. The Spouse field is created as a Contact, placed in the same Household (NPSP) and a Relationship is created between the Spouse and the Constituent. Households can be created automatically for every Constituent. With NPSP3  OTE creates Household Account records for spouses in the same household.

Relations: Mapped to Relationships (for Contacts) and Affiliations (Accounts). Event Participants: Mapped to Campaign Members. Appeals: Mapped to Campaigns. Campaign Members are created automatically. Campaigns (RE): The Raiser’s Edge Campaign table is available as an object called RE_Campain in OTE. You can download its CSV data and import it into whatever object you wish. Gifts: Mapped to Opportunities. Contact Roles are created automatically. Notes: Contact Notes and Donation Notes are supported. They appear among the importable objects. Importing these notes will automatically link them to the correct Contact or Donation record. You can also download notes as CSV files, as with all the other objects. Also, Raiser’s Edge allows notes without the “title” (or “subject”) field, but Salesforce does not. So when we transfer the note record over, if the note has no title, we take the first 30 characters of the note and make it the title in Salesforce, adding an ellipsis after it if needed.

Fund records, as seen in the above screen shot. But we do not yet have support for mapping Fund fields to Salesforce fields. For now, you can only download the Fund records in CSV format. These records can, of course, be imported into any Salesforce object, e.g., via Apsona for Salesforce. Tributes: You will be able to download a CSV file (there are 2 attribute tables in RE, you might want to consider a custom object to address it) or map the tributes to custom fields on the Opportunity. When filtering the data records in preparation for migration, we are now able to filter based on the Contact/Organization’s date added field, its inactive field, as well as the Donation’s date added field. Please see the screen shot below. If you apply a filter, say, for contacts created in 2012, that filter will carry through to all dependent records, i.e., only the gifts, campaign memberships and contact roles of the filtered list of contacts will be migrated when that filter is in effect.

Thus, using this filtering mechanism, we can now migrate data in chunks. For example, the first chunk of data for all contacts created in 2011, then in 2012, and so on. Note also that you can apply more than one filter term via the checkboxes. Filtering the Contacts/Organizations to migrate: In the second step of the migration wizard, you can now specify a filter condition via a where clause for the Raiser’s Edge records table before importing. See screen shot below. The where clause will be applied to the records table, so it can use any fields from that table directly. You can also use fields from other tables via subqueries in the where clause. You can use this feature in multiple ways; here are some example use cases: Before you perform a complete migration, you can run a small test batch to validate your mappings and other settings. You can do this, for example, via the where clause id <= 5 to select just a few records to migrate. The field id is the primary key of the records table in Raiser’s Edge, and is a positive number.

So specifying id <= 5 selects at most 5 records (possibly fewer, if some have been deleted). You can restrict the migration to just those contacts who have given donations since a specific date, e.g., February 1, 2004, via the where clause id in (select constit_id from gift where dte >= ‘2004-02-01’). This example uses a subquery on the gift table. You can migrate your data in batches when you have a very large source database. In the first batch, you apply (for example) the where clause id <= 25000; In the second batch, use id > 25000 and id <= 50000; If you need a “catch-all” where clause that covers all records, you can use id > 0. When you type in a where clause and click the Apply button, OTE fetches the record IDs matching the where clause and remembers them in browser memory. It also updates the record counts in the “Objects to migrate” table below, so that you can see the effect of using the where clause.  If you reload the OTE page, the remembered IDs and the where clause will be forgotten.

If you specify a where clause, you can only migrate Contacts, Accounts, and objects dependent on these two (such as Relationships, Affiliations and Donations); you cannot migrate objects such as Campaign and Fund that do not depend on the Contact object. So the recommended flow is that you first finish importing all the non-dependent objects, and then use the where clause (multiple times if necessary) for importing the Contact-related objects. If you’re having trouble with invalid mappings in step 3, remove the file web/cfg/sourceFieldsMap.js to cause OTE to forget its field mappings and start over. 2. Connect to the database (using the defaults) 3. You’ll get a screen that is a larger version of this: 6. Now your screen looks like this: 9. Expanding the correct DB will show all the tables: OTE now automatically detects whether the target system uses Causeview, the Non-Profit Starter Pack (NPSP), or neither. Causeview specific note: in Causeview, Tribute records are treated as special cases of Gift records.

So a Tribute is basically a Gift with a few additional fields. And Over the Edge migrates all Gift records anyway; for this reason, you must migrate Tribute records after you have migrated the Gift records. During the Tribute migration, Over the Edge extracts the tribute fields from the Raiser’s Edge database and simply updates the corresponding fields in the Gift object in Salesforce. In other words, there are no new Salesforce records created when migrating Tribute data. SQL Server Helpful Notes: Enabling JDBC connections on port 1433 Over the Edge requires access to the SQL Server database via JDBC, and that connection happens on port 1433. When SQL server is not configured to accept such connections, Over the Edge will fail with a “connection failed” error in step 2. To fix this problem, you might want to follow the steps described in this stackoverflow article or this one at the Microsoft Developer Network. Restoring a backup file Sometimes, when restoring a backup file from another installation, SQL server complains about ownership and file names.

In this example, I was trying to restore the backup file C:\Sridhar\RaisersEdge\RE7_db_db_201211141717-RPA.BAK into SQL server 2008.. So I had to run a script like the one below. The bold face section had to be added, and the target file names in the MOVE clauses had to be altered to match the source file name in each clause. RESTORE DATABASE [RPA_RE7] FROM  DISK = N’C:\Sridhar\RaisersEdge\RE7_db_db_201211141717-RPA.BAK’ WITH  FILE = 1,  replace, MOVE N’RE7′ TO N’c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\RPA_RE7.mdf’, MOVE N’re7_bio’ TO N’c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\RPA_RE7_bio.mdf’, MOVE N’re7_gift’ TO N’c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\RPA_RE7_gift.mdf’, MOVE N’re7_index’ TO N’c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\RPA_RE7_index.mdf’, MOVE N’re7_temp’ TO N’c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\RPA_RE7_temp.mdf’,