Known Issues · Eclipse IDE

Error: Property is referenced by visualforce page during deployment

Metadata , Eclipse IDE , Change Sets

Remove the property from the controller and remove it's reference from VF page then deploy the VF page and controller together - it throw below error during deployment. Error: "The property Boolean XXXXXXX is referenced by Visualforce Page (ELA_Checklist) in salesforce.com. Remove the usage and try...

In Review ·Reported By 109 ·Updated Today

SObjectType.getDescribe() or Schema.describeSObjects() do not correctly reflect the isAccessible, isCreateable, isDeletable, isUndeletable, isUpdateab

Apex , API , Platform , VisualForce , Eclipse IDE

Calling SObjectType.getDescribe() or Schema.describeSObjects() in Apex does not correctly reflect the objects' isAccessible, isCreateable, isDeletable, isUndeletable, isUpdateable properties (they always return as true, even if the user's profile has no perms on that object). This happens because...

In Review ·Reported By 51 ·Updated 3 days ago

Deployment error when deploying sharing rules together with queues on the same package

Packaging , Metadata , Eclipse IDE

When deploying sharing rules and queues together the following error can occurr error: "sharedFrom not allowed:queue - [QueueName]", when using ANT or the IDE.

In Review ·Reported By 9 ·Updated 7 days ago

Deployment of VF component fails with "Unsupported attribute" error

Packaging , VisualForce , Metadata , Eclipse IDE , Change Set , Change Sets

A deployment of visualforce components fails with an error: "Unsupported attribute myAttribute in <c:myComponent> in myVfPage at line 369 column 50"

In Review ·Reported By 36 ·Updated 8 days ago

Receiving Error when querying for lookup fields while using sObject.recalculateFormulas() method.

Apex , API , VisualForce , Eclipse IDE , Developer Console , Winter 16

Exception occurs when sObject.recalculateFormulas() is called and the query which retrieves the object contains reference fields. Example error: FATAL_ERROR System.UnexpectedException: Opportunity: bad field names on insert/update call: Account NOTE : If the fields are not updatable and they are...

In Review ·Reported By 126 ·Updated 9 days ago

User requests failing with Unable to lock row during deployment even though seeAllData=false in apex test classes

Metadata , Eclipse IDE , Change Set , Change Sets

-User requests sometimes fails with Unable to lock row when deployment/Validation in progress in org even though seeAllData=false in apex test classes. -This is caused by lock obtained on classes and triggers during deployment /validation.

In Review ·Reported By 14 ·Updated 10 days ago

Deployment fails in Summer 16 if Record Type has name as a single alphabet/character and is a part of Managed Package

Eclipse IDE , Summer 16

If a Record Type Name is a single alphabet or character, Eg. "E", and its full name is prefixed with a namespace in a metadata file, its deployment fails with the error : "The Record Type Name field can only contain underscores and alphanumeric characters. It must be unique, begin with a letter, not...

In Review ·Reported By 3 ·Updated 27 days ago

Custom Metadata Type cannot be deployed if it has validation rules

Custom Objects , Metadata , Eclipse IDE , Change Set , Change Sets

Custom Metadata Type cannot be deployed if it has validation rules.

In Review ·Reported By 20 ·Updated 2017-10-17

Metadata API Deployment fails from Spring '17 to Summer '17 with "Field:TagCsv must be Readonly"

Content and Files , Packaging , Metadata , Eclipse IDE , Summer 17 , Spring 17

If you have retrieved metadata from a Spring '17 (or prior) org, with ContentVersion Layout included, then deploy that package to a Summer '17 org, it fails with the following: Field:TagCsv must be Readonly

Fixed - Winter '18 ·Reported By 21 ·Updated 2017-10-14

Metadata API Deployment fails from Spring '17 to Summer '17 if an Assets Page Layout has one of the following fields set to Read-Only: Account, Produc

Packaging , Metadata , Eclipse IDE , Summer 17 , Spring 17

If you have retrieved metadata from a Spring '17 (or prior) org, with an Asset Page Layout that had the Account, Product2 or Contact fields set to Read-Only, then deploy that package to a Summer '17 org, it fails with the following: Field:AccountId must not be Readonly Field:Product2Id must not be...

Fixed - Winter '18 ·Reported By 12 ·Updated 2017-10-14

1 to 10 of 31 | Next

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.