If you have been using ADvendio for quite some time you might be reluctant to update to the newest version. But overall we recommend updating frequently (at least 2-4 times a year) to make sure that you can participate in the newest development, minimise bugs, and enable all new features. Please make sure to read the following notes before upgrading to a newer ADvendio Version:
* We are recommending the use of the Translation Workbench and overwrite/translate picklist values and record types. This will not be changed by the package upgrade. Additionally you can safely add your own values. Exception to this are global label values (see below).
Attention - Please abide the following update order:
Coming from a version lower than 2.58
Before updating ADvendio from a lower to the newest version you first need to install version 2.57.2. Please use the following installation links:
Coming from a version lower than 2.82.2
Before updating ADvendio from a lower to the newest version you first need to install version 2.82.2. Please use the following installation links:
Coming from a version lower than 2.104
Afterwards you will need to install version 2.104. Please use the following installation links:
Else you will receive an error message upon installation. Don't worry your data and current installation won't be affected by that error.
Updating to the latest ADvendio release might have caused a runtime error of your apex jobs.
If you are getting error messages similar to 'Ad-Server Delivery Report Lifetime' : Attempt to de-reference a null object Please reschedule the following APEX jobs:
You might get an error when try to upgarde to 2.93 or higher.
(ADvendioDashboards/cxymANPhZuiMbGdgdENRbfENDpTXQf1) You reached the limit for dashboards run as the logged-in user.
Depending on your Salesforce Edition you have a limit of dynamic dashboards set to 5 or 10. Dashboards which run as specific user are not counted. Solution: Deactivate your dashboards before installation and change back afterwards.
Message: (MediaCampaignExample) Duplicate Record Type
MediaCampaignExample: Duplicate Record Type
You manually created a sales path for the Media Campaign object, we added the path with version 2.85, if you're installing from a lower version and encounter this error you need to delete your path, install (a version that has the path disabled 2.102 and up) and afterwards create your own path using record types.
Concering picklist values on for the field status at Briefing script / Advertising Material you have to be very carefully. Salesforce does NOT allows you to use your own picklist values AND deactivate the ADvendio packaged picklist values!
Options:
otherwise you can not upgrade to a newer version.
The Limit of active lookups for an object reached (in one version we added 3 active lookups, which we later removed because of that error) This error will happen if you already have 5 active and required lookups for an object and then the package tries to add a new one. Can be solved be settings your lookups to optional.
The two errors when trying to skip the 2.82.2 installation before installing 2.83
This error occurs when you have created a custom field and ADvendio tries to add a new field / object with same API name.
To upgrade safely please adhere to the following recommendations:
In case of any questions, please don´t hesitate to contact us.
Pay special attention to all custom developments which might be interacting with ADvendio
Use the provided JavaScript API to embed your own business logic to the media configuration and commercial optimizer
Reschedule Apex Jobs for ADvendio classes after an update to ensure the correct function.
Don’t re-develop a function on your own that is already part of the ADvendio Package.
Don’t use the same API names for objects or fields in ADvendio objects which are already defined in the package. An object or field in an ADvendio object even without prefix (in its API name) will be considered part of a component of ADvendio which leads to incorrect behavior in ADvendio.
Avoid to use validations for "irrelevant" data-changes in order to prevent errors in automated processes (e.g. when validating an account phone number, check if the number had been changed - don’t start this validation if other fields have been updated only.)