Summer ’16

  • Salesforce Hacks: Using picklists to clean your data

    One struggle every Salesforce admin faces, is how to get users inputting the right data. Free form text fields with no format or structure to them. And then trying to report on these fields becomes a nightmare! So how do you then make sure your users are entering in the correct values? That is where the wondrous (yet often overlooked) field type called a ‘picklist’ comes in…

    say picklist again...

    And picklists within Salesforce can help you structure data while guiding your users to complete fields as needed. While recent releases have also added to their versatility. In turn, this can help you as an Awesome Admin setup your Salesforce data more effectively.

    So let’s go back to basics and dive in to Salesforce Picklists!

    You keep saying picklist!!!!!

    Let’s take a quick step back to make sure everyone has the same understanding of what a picklist is.
    A picklist is ultimately a way to present several values to the user, and restrict what then select as a value in the field.
    As an example, a status field when selected could show ‘To do’, ‘In Progress’ or ‘Done’ in the picklist.

    Two types to rule them all.

    Now we start getting into the fun stuff. And yes, I know I am a bit of a geek! In Salesforce there are two basic types of picklists available for an Admin to create, the regular ‘Picklist’ and ‘Multi Select Picklist’.

    The primary difference is illustrated below, where a ‘Picklist’ only allows one value to be entered at a time, while Multi-Select picklists allow a user to select more than one value.

    standard salesforce picklist
    A Standard Picklist allows a user to select one value.

    A Multi-select Picklist allows a user to select more than one value.

    Flexibility with global control

    Reuse the same picklist values across various picklist fields.

    Picklists and world domination… Not coming to a cinema near you!

    Seriously though, as you can hopefully see picklists give you a fair amount of flexibility. But what if you want the same picklist options available across different objects in Salesforce?

    As of Winter ’17 release, you can now define a common or global set of values for any picklist in your org to use. To do this for a new picklist you can go to:

    In Classic: Setup -> Create -> Picklist Value Sets
    Or in Lightning: Setup (via the little gear icon) -> Object and Fields -> Picklist Value Sets

    And as added extra, the Summer ’17 release allows you to promote any existing picklist values and turn it into a global value set. Simply go to the picklist you want to promote, and you will see a button on the top of the page.

    Promote an existing picklist to a Global Value Set.
    Promote an existing picklist to a Global Value Set.

    Picklist ‘gotchas’

    Picklists are very handy in ensuring your users add the right value into the field. But because of the way they are structured there are a few things to remember when setting up and using picklists.

    1) Record types:

    Have you ever wondered why one user will see an option in the drop down, but someone else can’t see that option? The combination of record type and the profile of the user defines what she/he will see on-screen! (Don’t worry though, this one gets even the most seasoned of admins.)

    2) Dependant picklists:

    Alternatively, it could be a dependant picklist. This is where the value of one field, controls what options are available in the second field. An example of this could be on an Opportunity – where you have two picklists – the ‘Stage’ field and ‘Lost Reasons’.

    You might want to display a list of ‘Lost Reasons’ if the user selects the ‘Stage’ of ‘Closed Lost’. Thereby allowing you to once again guide the user in what the valid options are.

    Enforce picklist values when loading data into Salesforce3) Using Dataloader and picklists

    Picklists are ultimately just text when Salesforce looks at it at the database level, so be mindful that when loading in values via Dataloader.

    Any new values in the file being loaded into Salesforce may appear unless you tick the ‘restrict picklist values’ option on the field (or setup a validation rule).

    4) Picklists in formulas

    Picklist values are technically stored as a text value in Saleforce, however when using them in any advanced formula within Salesforce, like a validation rule, remember to use the function ‘ISPICKVAL()’.

    For example, say we have a picklist field with the name ‘Industry’ and you wanted to see if a picklist value was set to ‘Financial Services’, you would use the formula like so: ISPICKVAL(Industry, “Financial Services’)

     

    So there we have it. In a few short minutes, we have covered the basics of picklists! Exciting right 🙂 Now go forth and structure your data! Any business that values data quality will thank you for it!

  • Reminder: Salesforce & TLS 1.0 being disabled

    As an #AwesomeAdmin – are you aware of which of your users is going to be affect by TLS 1.0 being disabled in Salesforce?

    Hopefully the answer is NONE!  But the July  22nd 2017 is fast approaching, have you gone through the checklist to ensure you are ready?

    First things first though.

    What is TLS 1.0?  And why should I care?

    Salesforce has an explanation on the Help article relating to TLS 1.0 being disabled:

    TLSTLS stands for “Transport Layer Security.” It is a protocol that provides privacy and data integrity between two communicating applications. It’s the most widely deployed security protocol used today, and is used for web browsers and other applications that require data to be securely exchanged over a network. TLS ensures that a connection to a remote endpoint is the intended endpoint through encryption and endpoint identity verification. The versions of TLS, to date, are TLS 1.0, 1.1 and 1.2.

    Salesforce web and API connections, along with email delivery, use TLS as a key component of their security. HTTPS (web) and STARTTLS SMTP (email) also use TLS as a key component of their security.

    In reality, what does this mean for you?  TLS is a protocol which provides security for you and your users when they log in to Salesforce.  This can be either via the website, like when a user goes to login.salesforce.com, or it is also used when a user logins to Salesforce via an app (like Salesforce for Outlook, Web to Lead, Open CTI, etc).

    After TLS 1.0 has been disabled, any login attempt using that protocol will simply fail, unless TLS 1.1 (as a minimum) is support.

    When is TLS 1.0 being disabled?

    Salesforce has previously moved the effective date for the TLS 1.0 disablement to give Admins more time to catch up, but I wouldn’t count on Salesforce moving this again.

    As it stands Salesforce are planning to disable TLS 1.0 on the 22nd July 2017.

    How do I check?

    In Summer ’16, Salesforce updated the Login History reports in Salesforce to allow Admins to check what type of TLS connection is used.  The downloaded file will also show you 6 months history, and will show the TLS Protocol being used.

    To access this, go to Setup -> use the Quick Find to search for ‘Login History’ -> Select ‘TLS 1.0 Logins Only’ -> Click the ‘Download Now’ button.  Please be mindful, this report can take a while to download if there is a lot of TLS 1.0 logins!

    Download Login History to find out if TLS 1.0 being disabled will impact you

    Hopefully, this is an empty or only a few records in the file for you.  One of the orgs I have recently managed had a lot!  And it was all down to Salesforce for Outlook needing to be updated for all users.

    From there, you should be able to narrow down what needs to be updated to then get it fixed.

    The good news, is most up-to-date browsers will already support TLS 1.1 or higher.  And the Salesforce apps like Salesforce for Outlook have supported this change for almost a year… If you are on the latest version of the software, it shouldn’t be a problem.

    Need more help?

    Because this has a potential big impact on customers, Salesforce has provided a lot of support documentation and guides.  They have even published a checklist to download and run through if you need more help.

Back to top button