ISVforce Guide

Introduction
ISVforce Quick Start
Designing and Building Your App
Packaging and Testing Your App
Passing the Security Review
Publish Your Offering on the AppExchange
Manage Orders
Managing Licenses
Provide a Free Trial
Supporting Your Customers
Upgrading Your App
About Package Versions
Creating and Uploading Patches
Working with Patch Versions
Publish Upgrades to Managed Packages
Pushing an Upgrade
About Push Upgrades
Push Upgrade Best Practices
Assigning Access to New Components and Fields
Sample Post Install Script for a Push Upgrade
Known Limitations for Push Upgrade
Scheduling Push Upgrades
View Push Upgrade Details
View an Organization’s Upgrade History
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Known Limitations for Push Upgrade

The following are known limitations when pushing an upgrade.
  • Settings for tab visibility are not carried over by permission sets. Hence, if your upgrade requires changes to tab settings, you can’t implement the changes automatically using a post install script. Instead, you’ll need to notify administrators to make the change manually.
  • Push upgrade fails if the package contains Visualforce markup that attempts to access the OpenActivity entity. For example, the following code in the package will cause the push upgrade to fail.
    1<apex:outputLabel for="taskDate" 
2value="{!$ObjectType.OpenActivity.fields.ActivityDate.label}" /> 

    As a workaround, avoid using the global ObjectType reference to obtain the label for OpenActivity.ActivityDate by specifying the label as follows:

    1<apex:outputLabel for="taskDate" value="Date" />