7.3.16 Breaking Change: Renaming of AdServer related objects into Connections (ADvendio Summer 2020 2.130)

What is changing?

With version 2.130 we’re going to rename many of the AdServer related fields and objects into something more general. The main changes will affect the objects AdServer Login and AdServer IDs.

In our new version those will be labled as:

  • Connections

  • Connection IDs

This will affect how these objects are named, but also affects other fields and buttons which are closely connected to these. For example lookup fields to formally called AdServer Login object will now also be called Connection. Same with Junction objects, like Selected Connection IDs. Also It could be, that to keep a coherent experience, some buttons will have a slightly different label.

See below, for a table of all the changed Objects, Fields, Buttons ect.

Note: If you are using custom translations for ADvendio (e.g. you translated ADvendio by yourself, in a language which is per default not offered by us) it’s likely that these changes won’t affect your translations and your users will continue to see these custom translations.

Why are we doing this?

Our integration to external systems has always been one of our main assets in ADvendio. As the media landscape is progressing, we are also witnessing a more complex landscape of different systems and players.

While in the past, it might have been enough for a publisher to have an AdServer connected, but now we are facing DSPs, SSPs, DMPs and many more. But also ADvendio got more flexible in it’s integration of external systems. We can now connect to SSPs and have started the integration of DSPs and Social Media as well.

To ensure a consistent experience for our customers and users, we decided to move to a more general naming for our objects and processes, if they concern more than just an AdServer.

Do I need to act? What do I need to do?

As we’re changing only the record type label and not the technical name, the change should not affect any functionality. As for our ADvendio features, we made sure that all vital processes, will adapt the change without issues.

Salesforce still offers a lot of possibilities for customization. If any of your own custom logic uses reference to the above mentioned Record Types, please check if your logic is using the Record Type API name and not the Labels. If you use Record Type Labels, you will need to enhance your logic to fit the new naming. Examples for these can be:

  • Custom Reports based on AdServer Login or Ad Type

  • Lightning Flows, which perform logic based on the AdServer in use

  • Workflow Rules

  • Custom Validation Rules

If possible we recommend, installing the new version in a sandbox environment, to familiarize yourself with the changes and test any custom logic or validations which might be affected. You can then use the chance to prepare a small messaging for your user base.

If you are feeling uncertain or need help in checking your customization, feel free to contact your Technical Account Manager or support@advendio.com.

What if I don’t want these changes?

As these are part of our ADvendio Managed Package, you will not have the option to enable or disable the new names.

However Salesforce still offers you ways to customize this. You can go to:

Setup → Translation Workbench → Override

and override the names of fields, objects, buttons and similar.

Detailed Changes:

2.128 and lower

Type

2.130 and coming

Comment

2.128 and lower

Type

2.130 and coming

Comment

AdServer Login

Object

Connection

 

AdServer Features

Field (object: AdServer Login)

Connection Feature

 

AdServer Job Information

Field (object: AdServer Login)

Connection Jobs Information

 

AdServer Login No.

Field (object: AdServer Login)

Connection No.

 

AdServer Price Field

Field (object: AdServer Login)

Price Calculation Field

 

Connected AdServer Login

Field (object: AdServer Login)

Related Connection

 

Generate DFP OAuth Token

Custom Button / Lightning Action (object: AdServer Login)

Generate Google OAuthToken

 

AdServer ID

Object

Connection ID

 

AdServer ID Name

Field (object: AdServer ID)

Connection ID Name

 

AdServer Login

Field (object: AdServer ID)

Connection

 

AdServer ID

Field (object: AdServer ID)

Legacy ID

We introduced a new ID field, which will replace this field in the future.

Currently the legacy field is still used by most existing integrations

Parent AdServer ID

Field (object: AdServer ID)

Parent ID

 

AdServer Name

Field (object: AdServer ID)

Technical Name

 

Ad Price AdServer ID Assignment

Object

Ad Price Connection ID Assignment

 

AdServer ID AdSpec Assignment

Object

Connection ID AdSpec Assignment

 

AdServer Team Assignment

Object

Connection Team Assignment

 

AdServerID AdvertisedBrand Assignment

Object

ConnectionID AdvertisedBrand Assignment

 

Content AdServerID Assignment

Object

Content ConnectionID Assignment

 

PublisherPayout AdServerID Assignment

Object

PublisherPayout ConnectionID Assignment

 

Selected AdServer ID

Object

Selected Connection ID

 

AdServer Exclusion

Object

Exclusion

 

AdServer Custom Field

Object

External Custom Field

 

Delivery Data

Object

Delivery Data

 

AdServer ID

Field (Delivery Data)

Connection ID

 

Enhanced Delivery Data

Object

Enhanced Delivery Data

 

AdServer ID

Field (Enhanced Delivery Data)

Connection ID

 

AdServer ID Name

Field (Enhanced Delivery Data)

Connection ID Name

 

AdServer ID Category

Field (Enhanced Delivery Data)

Connection ID Category

 

AdServer ID Type

Field (Enhanced Delivery Data)

Connection ID Type

 

Secondary AdServer ID

Field (Enhanced Delivery Data)

Secondary Connection ID