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 444 ·Updated Yesterday

Certain global value set names are restricted

Metadata

Certain global value set names are restricted and will cause ant deployment errors.

In Review ·Reported By 63 ·Updated Yesterday

Deleting a custom field/object should remove references with force:source:pull

Metadata

When we Delete a custom field / object from Scratch org that is not removing its references from other components like Profiles , Permission sets , Layouts etc..

In Review ·Reported By 43 ·Updated Yesterday

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 35 ·Updated Yesterday

Invalid field:TASK.WHAT_NAME in related list:RelatedActivityList when deploying ServiceAppointment layout

Activities , Metadata , Field Service

When deploying a page layout which includes an activities related list, the error "Invalid field:TASK.WHAT_NAME error when deploying page layout" may be returned. The entity may have TASK.WHAT_NAME included as a field in the default related list despite WHAT_NAME not being valid for that entity. This...

Scheduled - Winter '20 ·Reported By 29 ·Updated Yesterday

MD-API deploy error when lookup filter and searchLayout is changed

Packaging , Metadata

When you are deploying a package where lookup filters or searchLayouts are being changed, errors will be thrown in deployment. UnsupportedOperationException

In Review ·Reported By 3 ·Updated Yesterday

New!Deploying controlled picklist fields with altered picklist values is failing with error "control field "XXXXXXXX" is not found".

Metadata

SUMMARY: Deploying controlled picklist fields with altered picklist values is failing with error "control field "XXXXXXXX" is not found". - Actual Result Deployment fails with error "Error Message:- Control field value '****' not found, valid values are"[*****] - Expected Result Deployment...

In Review ·Reported By 1 ·Updated Yesterday

Filter with invalid operators are allowed to be saved during Entitlement Process creation and causing Bad boolean filter input error when deploy

AppExchange , Packaging , Metadata , Change Sets

- For the Case: Case Record Type Field the supported operators are only "equals to" and "not equals to". All other operators are not allowed. This validation is done when we are validating the Inbound Change list, but is ignored when creating the Entitlement Process. - Actual Result: User is able to...

In Review ·Reported By 21 ·Updated 5 days ago

Lightning Knowledge Article Smart Link's URL length varies with added parameters

Service , Knowledge , Metadata , Communities , Lightning

In Lightning internally or in a Lightning template based community, clicking a Smart Link from one Knowledge article to another results in the browser's URL varying in length (and can be quite long) with additional parameters. This number of parameters contained in the URL are related to the number...

In Review ·Reported By 9 ·Updated 6 days ago

Package install failed if LWC imports Apex method and subscriber has the same named Apex class with no namespace

Apex , Metadata , Lightning

Package install failed if LWC imports Apex method and subscriber has the same named Apex class with no namespace. Actual Result: The no namespace class is looked up and the package install is failed Expected Result: The class in the namespace is looked up and package is installed

In Review ·Reported By 3 ·Updated 6 days ago

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