Metadata API deployment with mismatched Forecast Category picklist values can cause internal server error
Last updated 2014-12-23 ·Reference W-2274696 ·Reported By 2 users
When deploying changes using Metadata API (Eclipse, Ant....) you might run into issues if the Source and Destination orgs have different "Forecast Category" picklist values in the Opportunity object.
The internal server error received for this issues usually contains the following reference: (681828328)
1. Deploy, using Metadata API, from one org where the Forecast Category picklist values are different to the destination organization.
2. The destination org will accept the deployment but the issue will appear.
- One way to identify the issue is via the internal error: (681828328)
- On the page of Opportuniy -> Fields -> Forecast Category
In "Status Category", some rows shows:
__MISSING LABEL__ PropertyFile - val null not found in section ForecastCategory
To prevent this issue from happening please make sure that on both organizations (source/destination), the Forecast Category picklist values are exact same values.
If you are already seeing this error please create a case with Support so we can assist you on this.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.