We are pleased to present below all posts tagged with 'mapping'. If you still can't find what you are looking for, try using the search box.
Using Global Option sets in CRM 2011 can simplify the process of mapping option sets. But what if you have a local option set in one entity and a global option set in another? This blog explains how to map data from a local option set in one entity to the equivalent in another via workflow.
On a recent Salesforce implementation, we identified a need to map a single lead field to two different fields - one on the contact and one on the opportunity.My initial thought was to create a trigger to fire on lead conversion that would populate the second field. However, I always try to look first for a non-coding solution. Which brought me to the fairly simple idea of creating a second field that would use a workflow field update to copy the value of the original field. The new field would be hidden from the users, but would be used for the sole purpose of mapping to the second destination field. I thought I'd found the perfect "clicks not code" solution ...until I realized my field was a lookup field, a field type that can't be updated by workflow. Drat.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.