1. Once enabled, Multi-Currency can’t be disabled for your organization.
2. Work with your salesforce.com representative to determine the best time for Multi-Currency enablement. The enablement process temporarily locks your organization, preventing any integration processing and user logins. The lockout duration depends on the data space used by your organization. This table shows the lockout durations and recommended times for enablement.
3. Upon enablement, all existing records are stamped with a default currency code that you provide in your enablement request. For example, if your organization contains records using USD and EUR, you need to switch them all to the same default currency prior to enablement. Support for this type of conversion is also available as a salesforce.com paid implementation service.
4. Objects that support multiple currencies include Opportunities, Opportunity Products, Opportunity Product Schedules, Campaign Opportunities, and reports related to these objects and fields. By default, page layouts for these objects have multiple-currency compatible fields, which allow you to specify the currency for the record. Typically, these fields are available only when creating a new record or editing an existing record. The selected currency is used for the primary amount field.
5. After enablement, the primary currency displays as usual followed by the secondary currency amount in parentheses. The primary currency is typically the default corporate currency, unless it’s overridden at the record level. The secondary currency amount shown in parentheses is always the user’s personal default currency, calculated based on the conversion rate settings defined in your
organization.
6. In reports, the primary currency reflects either the default corporate currency or the currency selected for the record. The secondary currency reflects the personal default currency of the user running the report, or the currency specified in the report criteria. 7. Dated exchange rates are used for opportunities, opportunity products, opportunity product schedules, campaign opportunity fields,
and reports related to these objects and fields. Dated exchange rates are not used in forecasting, currency fields in other objects, or currency fields in other types of reports.
8. Organizations with advanced currency management support roll-up summary fields between two advanced currency management objects. For example, roll-up summary fields are supported from an opportunity line object to its opportunity object, because both are advanced currency management enabled. However, if you enable advanced currency management, you cannot create roll-up summary fields that calculate currency on the opportunity object rolling up to the account object. All existing currency-related roll-up summary fields on the opportunity object are disabled and their values are no longer calculated. If your organization enables advanced currency management, you should delete any currency roll-up summary fields using opportunities and accounts or opportunities and custom objects.
9. Campaign opportunity fields use dated exchange rates when calculating the amount in the campaign currency, but are not used when converting those amounts to the user currency.
10. Cross-object formulas always use the static conversion rate for currency conversion.
11. If advanced currency management is enabled, you can't bind Visualforce pages that use <apex:inputField> or <apex:outputField> components to currency fields that support advanced currency management.
12. By default, your quota amounts display in your personal currency. You can change the currency of your quota to any of your organization’s active currencies. When you change the currency, the corresponding forecast is also changed to the new currency. 13. When creating list views or custom reports, you can use the list view Search Criteria or filter logic in report builder to limit your data
to items with specific currencies or amounts. For example, you may create a list view of all opportunities with amounts over 100,000 U.S. dollars. To do this, you need to follow these rules:
a. Prefix currency amounts with a currency code, for example, Annual Revenue greater than USD 50000000.
b. Without the currency code, all amounts are assumed to be in the user's personal currency. For example, Annual Revenue greater than 50000000 means 50 million U.S. dollars, assuming the user's personal currency is U.S. dollars.
c. All amounts are converted to the corporate currency for comparison. For example, Annual Revenue greater than USD 50000000 finds accounts with revenue greater than 50 million U.S. dollars. This would include an account with revenue of 114 million Australian dollars, which is the equivalent of 60 million U.S. dollars, assuming a conversion rate of 1.9. d. Use the Currency field to find items with a particular currency, for example, Opportunity Currency equal AUD finds
opportunities with amounts in Australian dollars.
14. For personal imports, all amounts in new accounts and contacts are imported in your personal currency. When import updates amounts in existing records, the amounts in your file are converted from your personal currency to the currency of the account or contact. For example, your personal currency is U.S. dollars, and your import file has 100 as the annual revenue of an existing account with Account Currency of Finnish marks. The new Annual Revenue value of the account is 600 FIM, assuming a conversion rate of six Finnish marks to one dollar.
15. For accounts and contacts, you can use an active or inactive currency code. You must use an active currency code for leads. 16. The Currency ISO Code column applies to both the account and contact. You cannot specify different currencies for associated
contacts and accounts.
17. During import, you cannot update the Currency field for existing accounts and contacts. 18. Creating new accounts, contacts, or leads:
a. If you do not use the Currency ISO Code column or fail to map it, any amounts are imported in the corporate currency. For example, if the corporate currency is U.S. dollars, and the value in your file is 100, this is imported as 100 USD.
b. If you enter an inactive currency, any amounts are converted to the corporate currency. For example, if your file has 100 AUD, this is imported as 50 USD, assuming the corporate currency is U.S. dollars and Australian dollars is an inactive currency with a conversion rate of 0.5.
19. Updating existing accounts and contacts:
a. If the currency code in your import file does not match the existing currency of the record, any amounts will be converted to the currency of the record. For example, if the import file has 100 GBP and the record has a currency of FIM, the amount is imported as 950 FIM, assuming a conversion rate of 9.5.
b. If you do not use the Currency ISO Code column or fail to map it, any amounts are interpreted as the corporate currency and then converted to the currency of the record. For example, if your file has 100 for a record that has a currency of FIM, this amount is interpreted as 100 USD and then converted to 650 FIM, assuming the corporate currency is U.S. dollars and Finnish marks has a conversion rate of 6.5.
20. If Advanced Currency Management is enabled, you can use dated exchange rates to map a conversion rate to a specific date range.
Language
1. Salesforce.com offers three levels of language support: fully supported languages, end user languages, and platform-only languages. All languages are identified by a two-character language code (such as en) or a five-character locale code (such as en_AU).
2. For end user languages, Salesforce provides translated labels for all standard objects and pages except Administration Setup and Help. End user languages are useful if you have a multilingual organization or partners who speak languages other than your company’s default language.
3. Platform-only languages are used when you want to localize custom functionality (apps) that you’ve built on the Salesforce platform. When you choose a platform-only language, Salesforce provides translations for all of the custom objects and field labels in the chosen language.
4. When you specify a platform-only language, labels for standard objects and fields fall back to English except: English (Australia), English (India), English (Malaysia), and English (Philippines) fall back to English (UK); French (Canada) falls back to French; Moldovan falls back to Romanian; and Portuguese (European) falls back to Portuguese (Brazil).
۞ Files –
o Upload a file in Chatter and store it there privately until you're ready to share it. o Share the file with coworkers and groups to collaborate and get feedback.
o Attach files to posts in a Chatter feed on the Home tab, Chatter tab, a profile, a record, or a group. ۞ Salesforce CRM Content –
o Create, clone, or modify a sales presentation and save it so only you can see it and work on it.
o When you're ready, publish it so other users in your company have access to it. Create a content pack and send it to customers.
۞ Salesforce Knowledge –
o Write, edit, publish, and archive articles using the Articles Management tab or find and view published articles using the Articles tab.
o Customers and partners can access articles if Salesforce Knowledge is enabled in your Customer Portal, partner portal, Service Cloud Portal, or Force.com Sites.
o Create a public knowledge base so website visitors can view articles. ۞ Documents –
o Store Web resources, such as, logos, DOT files, and other Visualforce materials in folders without attaching them to records. ۞ Attachments –
o Add a file to a specific record, like an event, marketing campaign, contact, or case by attaching it on the Attachments related list.