#DUPLICATE DETECTOR SALESFORCE PROFESSIONAL#
#DUPLICATE DETECTOR SALESFORCE WINDOWS#

Geekiest feature - can print unique barcodes for your bottles and use a scanner to check them in and out.Surprise & Delight feature - the ability to print a restaurant-style wine list.

#DUPLICATE DETECTOR SALESFORCE WINDOWS#

Drinking windows - updated by users, partnership with review publications to overlay their data for subscribers of their content.

Wine valuations - partner with Wine Market Journal for appraisals, overlaid with what people are paying for the wines in CellarTracker.

Features collectors use - what wines do they have, when do they want to drink them, what are wines worth (the main premium feature).

Most used features - tasting notes (~10M visitors/year on the website, most people reading or researching the tasting notes ~9.1M tasting notes growing ~750k / year / ~2k / day).

Optical recognition of labels - partners with Vivino.

#DUPLICATE DETECTOR SALESFORCE PROFESSIONAL#

9.1M tasting notes in the community + 1.3M professional tasting notes.

Byproduct - вЂњYelp for wineвЂќ - the aggregated wisdom of the community from tasting notes, drinking windows.

Core element - a productivity tool to catalog and manage every aspect of the wine experience (e.g., purchasing, tracking, consuming).

Eric created CellarTracker while on sabbatical from Microsoft in 2003, then in April 2004, launched it publicly and left Microsoft a few months later.Built a tool to keep track of his cellar, then let a few friends use it, which morphed a personal spreadsheet into a relational database.1999 - took a biking trip to Tuscany and fell in love with wine and started collecting.He was at Microsoft from 1992 - 2005 his last project was the вЂњsend error reportвЂќ feature.EricвЂ™s openness and candor provide an in-depth look at how one of the leading wine platforms was founded, built, and where itвЂ™s going next. Yet, heвЂ™s built one of the most useful productivity tools for wine collectors, an engaged community of geeky wine lovers, and a respectable business that heвЂ™s now investing in to grow and take to new heights for the benefit of the CellarTracker community.

You will have to follow the same steps for each duplicate rule that is preventing Leads from converting.Building the app while on sabbatical from Microsoft in 2003, Eric LeVine, CEO and founder of CellarTracker, had been close to a one-person show until recently. You may have to add several conditions - for example, if you have several different record types coming for Soapbox, Soapbox Donations, Soapbox Registration, etc.ДЄlso note that you may have more than one duplicate rule. An example might be 'Lead Record Type - not equal to - Soapbox Donations'

Set the Field, Operator and Value to something that would be specific to incoming Soapbox data.

Scroll down to the 'Conditions' section.

With the rule still open from step 3 above, click the 'Edit' button.

Note that Soapbox has it's own matching strategy, so you shouldn't need to monitor incoming Soapbox data for duplicates.

Create a 'condition' that will exempt Soapbox records from triggering this rule.

If you see that there is a Duplicate Rule such as described above, and the Alert checkbox is checked, then this is likely your issue.

Note that the 'Alert' option is likely selected.

Note that the Alert Text matches what you saw in the error message.

They may be named something along the lines of: 'Standard Rule for Leads with Duplicate Contacts', or 'Standard Rule for Contacts with Duplicate Leads'

Look for Rules that are affecting Leads, or Contacts.

In Salesforce Setup, navigate to your Duplicate Rules.

To resolve this, first identify the duplicate rule that is causing the issue: This situation is preventing your Lead from converting. This means that any time a Soapbox transaction is sent to Salesforce when there is a matching Lead, this rule will throw an 'alert' - effectively halting the Lead conversion process. That rule is being triggered, and has the 'Alert' option selected. TheВ error message 'DUPLICATES_DETECTED, Use one of these records?' or similar is being triggered by a duplicate rule that you have active in your Salesforce instance.

Duplicate detector salesforce