Release notes for Episerver updates

When you configured a visitor group, an error occurred if duplicate field names were present in the marketing provider.

In Eloqua, the Company field is mapped to the accountName parameter. If you have both Company and accountName fields in your Eloqua instance, an error occurs.

Note: To map a form field to Company, use the accountName field from the datasources dropdown.

Delivra Connector: Form field mapping and visitor groups UIs should show display names of fields.

In the Eloqua connector, for a contact, only fields with a value are being returned. As a result, visitor groups with a criterion based on a field not having a value (for example, Null or Empty) are not matched correctly.

The datasources dropdown on the Visitor Group Profile Criteria configuration screen for Silverpop lists only parent level databases. The dropdown should also display child contact lists.

There are multiple calls to dynamic data store to fetch the connector credentials. Use caching to reduce the number of calls.

There are multiple calls to dynamic data store to fetch the list of active connectors. Use caching to reduce the number of calls.

Steps to reproduce
1) Go to any connector's Admin settings screen, for example, Admin -> Config -> Microsoft Dynamics CRM.
2) Add settings and save.
3) Refresh the page.
4) Click Add Connector. An empty settings box appears.
5) Without saving anything, click the Microsoft Dynamics CRM link in the left navigation. The empty settings box remains on the screen.
6) Click the "Microsoft Dynamics CRM" link again. The empty settings box disappears.

Expected
The empty settings box disappears after the first click on the Microsoft Dynamics CRM link.
Also, after the first click, when the empty settings box remains on the screen, if valid values are entered and "save" button is clicked, the box disappears, leaving only the previously saved settings box on the screen. That is, the new instance is not saved.

Actual
See steps to reproduce

The new properties on the global settings UI are not saved when upgrading from EPiServer.ConnectForMarketingAutomation 5.4.0 to 5.5.0.
They work only on a fresh installation of 5.5.0.

Currently, if the submission of form data to a marketing connector to create/update an entity is unsuccessful, it logs an error but still shows a success message in the UI. Also, the form submission is recorded in the Epi database.
Provide an option via the Admin settings to choose a different behavior, such that the error is displayed in the UI, and the form submission is not recorded in the database.