Versions Compared

Old Version 6

changes.mady.by.user Former user

Saved on

compared with

New Version 7

changes.mady.by.user Pascal Clausen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

This error occurs when you have created a custom field and ADvendio tries to add a new field / object with same API name.

Upgrade Order

Attention - Please abide the following update order:

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.


3. How to make sure that you can safely upgrade to newest version of ADvendio?

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 to make sure that you can participate in the newest development, minimise bugs, and use all new features. 

To upgrade safely adhere to the following guidelines:

Do’s

Dos

  • Keep as close as possible to the standard.
  • Think about changing internal processes first before changing the system.
  • Before developing custom functionalities on your own, ask you ADvendio consultant if there is already something similar on the roadmap or if ultimately an existing feature could be enhanced.
  • Read the release notes carefully.

    • 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 a sandbox to test a new version before installing it in production
    • and define recurring test cases for core business processes.
    • Refresh your sandbox before installing a release
    • and think about relevant test-data.
  • Determine your own release cycle and reserve resources (especially human resources) to implement own development and Advendio releases.
  • Use as many as possible of the embedded standard workflows and processes

  • 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'ts

  • Don’t install a release without testing it in a sandbox!
  • Don’t integrate Custom JavaScript in the Media Configuration which works contrary to logic, workflows or processes in the standard of the ADvendio package.

  • Don’t re-develop a function on your own that is already part of the ADvendio Package.

  • Don’t re-use the same API name 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.)


4. How to adapt or enable new ADvendio features

Some of the new features can't be packaged in Salesforce and therefore need manual work in order work correctly. Especially if you are upgrading and not installing a first version, some values have to be manually set. The first step is to read newest Change Logs.  Change logs can be found next to the release notes in the corresponding seasonal release folder. The Change Log lists all values and fields which you need to consider if you like to introduce a new feature. 
So please consider the following hints if the new feature uses:
  1. Record types you might have to
    1. add them manually using the correct spelling from the change log and
    2. translate or overwrite the value into local language
    3. adjust the access rights for the corresponding user profiles. 
  2. Additional picklist values, make sure to
    1. add them manually using the correct spelling from the change log and
    2. translate or overwrite the value into local language
    3. add them to the correct record type(s)
    4. and adjust the access rights to the profiles which need.
  3. New fields or deprecated fields in Layouts
    1. Adjust your layouts appropriately to add new fields and their visibility. 


...