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 387 ·Updated Today

Napili Community - Unable to play videos within the community when using VF

Communities , Summer 17 , Spring 17

Unable to play the videos within the community using Napili template, videos are embedded in a VF page. The video is played successfully if executed from the VF page in Classic and LEX.

In Review ·Reported By 4 ·Updated 2 days ago

Spring '17 Visualforce Pages appearing in Lightning when not flagged to do so.

Mobile , VisualForce , Spring 17 , Lightning

In Spring 17, Visualforce being used on record detail pages A are visible in Lightning Experience and other Lightning based apps, such as Communities even if they have not been flagged to be visible. It still works correctly for Mobile Apps.

In Review ·Reported By 13 ·Updated 10 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 2018-05-17

Error "In field: excludeButtons, no such standard action:Activate" thrown when attempting to deploy and Order page layout.

Metadata , Change Sets , Spring 17

When attempting to deploy a change set that includes a page layout for the Order standard object the user may encounter the following error: "In field: excludeButtons, no such standard action:Activate"

Fixed - Summer '17 ·Reported By 16 ·Updated 2018-05-17

Deploying Person Account recordType failing with error: Field <Global picklist> in 'Account' cannot be resolved to a picklist field or global picklist

Metadata , Eclipse IDE , Change Sets , Spring 17

When deploying custom record Type to a Spring 17 sandbox from a Winter 17 sandbox ,it is failing with error Field <Global picklist value> in 'Account' cannot be resolved to a picklist field or global picklist

Fixed - Spring '17 Patch 6.0 ·Reported By 5 ·Updated 2018-05-17

Change set fails to upload in Professional Edition if Assignment rules are included.

Change Sets , Spring 17

In Professional edition assignment rules will not show in the added components for a change set, and a change set will fail to upload if assignment rules are included.

In Review ·Reported By 1 ·Updated 2018-05-17

Spring 17 - Community fails to render properly post upgrade to Spring 17

Communities , Spring 17

Some customers may have observed that post upgrade to Spring 17, their community which use the Customer Service ( Napili) Template no longer seems to render properly. In some situations , it may seem that everything is crammed towards the center of the page making the community practically unusable. This...

In Review ·Reported By 15 ·Updated 2018-05-11

Lightning UI, scrolling through picklist values makes the entire page scroll

User Interface , Spring 17 , Lightning

While in Lightning, when picklist fields have a lot of values and it requires you to scroll, the entire screen will scroll as well.

In Review ·Reported By 30 ·Updated 2018-05-10

Deploying Account and Contact OWD in the same deployment package may fail

Change Sets , Spring 17

Deploying Account and Contact OWD in the same deployment package may fail with message as " Deployment error: ReadWrite is not a valid sharing model for Contact when Account sharing model is Private"

In Review ·Reported By 1 ·Updated 2018-04-24

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