Deployment Error: The user license doesn't allow the permission: SubscribeToLightningReports

Metadata , Spring 17

When deploying profiles or permission sets linked to Partner and Customer licenses to a Spring 17 destination org , it fails with an error Error attempting to validate change set: The user license doesn't allow the permission: SubscribeToLightningReports

In Review ·Reported By 377 ·Updated Yesterday

Unable to find List View to add to Change set to Outbound Changesets if it is a member of a Queue

Metadata , Change Sets

Some customers may have observed that they are unable to add List Views to Outbound Change Sets if the List View Contains any value(other than --None--) in the Queue dropdown under Filter By Owner section.

In Review ·Reported By 155 ·Updated Yesterday

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 Remove the usage and try...

In Review ·Reported By 139 ·Updated Yesterday

"Duplicate value found" Error during deployment of the Status standard picklist values on a Contract standard object


During the deployment of the new values for the standard picklist field "Status" of the standard object "Contract" using Metadata API (ANT) we get the "duplicate value found" error.

In Review ·Reported By 27 ·Updated Yesterday

Updating Managed Custom Metadata Type Record via Metadata.Operations.enqueueDeployment() fails when record's Language field doesn't match org language

Apex , Metadata , Summer 18

The Custom Metadata API tries to update the Language field of the record to the current language of the org every time the record is updated. In managed records, this field is not writeable. If the language of the org matches the Language field value of the CMT record, then there are no problems (because...

Scheduled - Summer '18 Patch 7.0 ·Reported By 22 ·Updated Yesterday

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"

In Review ·Reported By 62 ·Updated 4 days ago

The Inbound change sets are not accessible for newly uploaded change sets from Spring 17 to Winter 17 org.

Metadata , Change Sets , Winter 17 , Spring 17

After Spring 17 , the newly created change sets which when moved from spring 17 orgs to an winter 17 org . The inbound change sets pages are not accessible and giving an ISE like: Error ID: 87452590-127216 (2080591907)

Fixed - Spring '17 Patch 3.2 ·Reported By 86 ·Updated 5 days ago

Incorrect ordering of custom metadata picklist fields in SOQL


Documentation shows that when using ORDER BY, picklist sorting is defined by the picklist sort determined during setup: However with this issue the order that is observed is different....

In Review ·Reported By 17 ·Updated 4 days ago

Poor performance when opening inbound change set setup section and deployed change set details

Packaging , Metadata , User Interface , Change Sets

Users may see a delay ~5-10+ second delay when initially opening the Inbound Change Set setup section and when attempting to open deployed change set details (15-20+ seconds).

In Review ·Reported By 4 ·Updated 4 days ago

Error: profiles/Admin.profile(Admin):The user license doesn't allow the permission: CreateWorkBadgeDefinition

Metadata , Eclipse IDE , Spring 14 , Change Sets

When using the Ant/ Changeset/ 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 58 ·Updated 5 days ago

1 to 10 of 160 | 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.