Data Set Strategy
When starting to use Geopointe, the process of setting it up to get your desired mapping results may seem overwhelming. In actuality, though, you have the keys to building a cohesive and familiar library of data sets for your users that mirrors the rest of your Salesforce system.
Before touching Geopointe, look at your Salesforce data and take note of your current organization models.
- Look at your object list views. How is that data segmented?
- Look at your reports. What kind of comparisons do you run on a regular basis?
- How is your data categorized? By their status/stage? By record type? By territory or region?
Take note of these segments and how your company already sorts the data. Successful data sets are going to mirror established organization techniques and create familiarity and common threads between Geopointe and the rest of Salesforce.
Base Data Sets
Less is more is a good strategy to stick to when deciding how many org-wide data sets to create. Consider the number of list views and reports you have. Narrow those down to:
- Views that are used on a daily, perhaps weekly, basis.
- Views and reports that will be valuable in geographic form.
- Less-commonly used—but important—reports that have complex filters.
Having a Data Set Selection drop-down that includes a long list of data sets is going to be overwhelming to your team, and they may lose patience when trying to find the one they’re looking for. Choose the data sets that everyone will need access to with care. Having a smaller, digestible list of data sets will strengthen productivity and alleviate frustration.
Remember that the data set filters are not the only important setting to consider. Consider when it is appropriate to make color markers by the default, and which fields should be available in the search results. Important fields placed on views and reports should carry over to their data set counterparts.
Make Them Your Own
Give your team the tools they need to build personal data sets to their liking. Having the library of org-wide data sets should be the kick-off point. Then show them how to have their own list of data sets important to their needs.
End users can create a data set in one of two ways:
- Editing and making changes to an org-wide data set, then clicking Save As to make it their own.
- Clicking the + button on the map control panel and creating a new data set from scratch.