Set Up and Maintain Your Salesforce Organization Mass Update Addresses
Mass Update Addresses
When your data is consistent, your reports and related metrics are more accurate and easier to understand. For example, having different abbreviations for a country or state can skew your data.
To make your addresses consistent, you can update country and state/province information in existing fields at one time.
You can mass update addresses in contacts, contracts, and leads.
Tip: To ensure data consistency in new records, consider using state and country picklists.
EDITIONS
Available in: both Salesforce
Classic and Lightning
Experience
Available in: All Editions except for Database.com.
1. From Setup, enter
Mass Update Addresses
in the
Quick Find
box, then select
Mass Update Addresses.
2. Select Countries or State/Province. If you chose State/Province, enter the country in which to update the state or province.
3. Click Next.
4. Select the values to update and click Add. The Selected Values box displays the values to update.
The Available Values box displays the address values found in existing records. To find more addresses to update, enter all or part of a value and click Find.
If your organization has large amounts of data, instead of using the Available Values box, enter existing values to update in the text area. Separate each value with a new line.
USER PERMISSIONS
To mass update addresses:
•
Modify All Data
To mass update addresses of contracts:
•
Modify All Data
AND
Activate Contracts
5. In the Replace selected values with field, enter the value with which to replace the specified address data, and click Next. If your organization has large amounts of data, this field is called Replace entered values with.
The number and type of address records to update are displayed. If you have large amounts of data, only the values to update are displayed.
6. Click Replace to update the values.
SEE ALSO:
Let Users Select State and Country from Picklists
Scalability FAQ
•
How scalable is Salesforce?
•
Will I see a degradation in performance as Salesforce’s subscriber base grows?
How scalable is Salesforce?
The service has the capacity to scale to the largest of teams. The architecture behind the service was designed to handle millions of users. We scale as rapidly as our customers require.
Will I see a degradation in performance as Salesforce’s subscriber base grows?
No. We are very conscious of performance and have designed the service to be scalable in such a way that we can constantly stay ahead of customer demand. Our architecture allows us to easily add web and application servers to accommodate more users. The system architecture also allows us to add more database servers as needed to accommodate more users. In addition, the facility that houses our servers provides us with guaranteed bandwidth, which we can increase as needed.
471
Set Up and Maintain Your Salesforce Organization Cache Force.com Data
Cache Force.com Data
Using the Platform Cache can enable applications to run faster because they can store reusable data in memory. Applications can quickly access this data, removing the need to duplicate calculations and requests to the database on subsequent transactions.
To use Platform Cache, first set up partitions using the Platform Cache Partition tool in Setup. Once you’ve set up partitions, you can add, access, and remove data from them using the Platform Cache Apex API.
Use Platform Cache partitions to improve the performance of your applications. Partitions allow you to distribute cache space in the way that works best for your applications. Caching data to designated partitions ensures that it’s not overwritten by other applications or less-critical data.
To access the Partition tool in Setup, enter
Platform Cache
in the
Quick Find
box, then select Platform Cache.
Use the Platform Cache Partition tool to:
•
Request trial cache.
•
Create, edit, or delete cache partitions.
•
Allocate the session cache and org cache capacities of each partition to balance performance across apps.
•
View a snapshot of the org’s current cache capacity, breakdown, and partition allocations (in KB or MB).
•
View details about each partition.
•
Make any partition the default partition.
To use Platform Cache, create at least one partition. Each partition has one session cache and one org cache segment and you can allocate separate capacity to each segment. Session cache can be used to store data for individual user sessions, and org cache is for data that any users in an org can access. You can distribute your org’s cache space across any number of partitions. Session and org cache allocations can be zero, or five or greater, and they must be whole numbers. The sum of all partition allocations, including the default partition, equals the Platform Cache total allocation. The total allocated capacity of all cache segments must be less than or equal to the org’s overall capacity.
You can define any partition as the default partition, but you can have only one default partition. When a partition has no allocation, cache operations (such as get and put) are not invoked, and no error is returned.
Capacity calculations occur every 5 minutes by default. To make sure you’re seeing the latest capacity and allocation, click Recalculate.
IN THIS SECTION:
Request a Platform Cache Trial
To test performance improvements by using Platform Cache in your own org, you can request trial cache for your production org.
Enterprise, Unlimited, and Performance editions come with some cache, but adding more cache often provides greater performance.
When your trial request is approved, you can allocate capacity to partitions and experiment with using the cache for different scenarios. Testing the cache on a trial basis lets you make an informed decision about whether to purchase cache.
Purchase Platform Cache
You can purchase Platform Cache space to improve the performance of your application.
SEE ALSO:
Apex Developer Guide
472
