Known Issues · Eclipse IDE
Metadata , Eclipse IDE , Spring 14 , Change Sets
When using the Ant/ Changeset/ Force.com IDE deploy tools to deploy the System Administrator (Admin) profile into a Spring '14 sandbox/ production, We see this error reported: Error: profiles/Admin.profile(Admin):The user license doesn't allow the permission: CreateWorkBadgeDefinition
In Review ·Reported By 73 ·Updated 4 days ago
Invalid target dialog reference error when deploying Einstein Bot Version.
Eclipse IDE , Change Sets , Einstein Bots , Winter 20
Some customers may have observed that they see the following error when attempting to deploy(Validate) their Change set containing an Einstein Bot versions. API Name Type Line Column Error Message XYZ.v1 Bot Version 1658 45 Invalid target dialog reference: Dialog_Name The Winter '20 release...
Fixed - Winter '20 Patch 7.0 ·Reported By 0 ·Updated 7 days ago
Sharing , Eclipse IDE , Change Sets
You will receive the following email notification when you deploy change of a custom field relationship from Lookup to Master Detail by deployments, such as change sets, Force.com IDE and Force.com Migration Tool. "Your request to change your organization-wide sharing defaults was unsuccessful, please...
In Review ·Reported By 3 ·Updated 19 days ago
Analytics , Metadata , Eclipse IDE
The issue is that errors seen while submitting translations for CRT labels may be misleading when section names are duplicated in report types or column names are duplicated in translations that refer to report types. The error message(s) may not point to the right report type or the right section and...
In Review ·Reported By 24 ·Updated 2022-07-14
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...
Fixed - Winter '19 ·Reported By 128 ·Updated 2022-02-10
Deployment of VF component fails with "Unsupported attribute" error
Packaging , VisualForce , Metadata , Eclipse IDE , Change Sets
A deployment of visualforce components fails with an error: "Unsupported attribute myAttribute in <c:myComponent> in myVfPage at line 369 column 50"
Fixed - Winter '19 ·Reported By 68 ·Updated 2022-02-10
Apex , AppExchange , Packaging , Metadata , User Interface , Eclipse IDE , Change Sets
Metadata deployments via change sets or packages may show that the deployment was successful without any error messages. However, upon checking - the expected components are not actually deployed or present in the target org. This may occur if your change set contains Apex and requires the deploy...
Fixed - Summer '20 ·Reported By 26 ·Updated 2022-02-10
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 2022-02-10
Apex , Eclipse IDE , Change Sets , Spring 16
Compiling an apex class which refers to the User.Account foreign key in an inline query fails with the ApiQueryException exception, "Didn't understand relationship 'Account' in field path...", if some class which refers to some foreign key in User and whose API version is 31.0 or prior has been compiled...
Fixed - Spring '19 ·Reported By 16 ·Updated 2022-02-10
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 2022-02-10
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.
