Salesforce Known Issues

Known Issues · Marketing Cloud Audience/Contacts

Contacts Delete Settings will not retain 0 days

Marketing Cloud Audience/Contacts

When selecting 0 days in Contacts Delete Settings, you will notice it is reverted back to 30 days. This is a UI bug only. The suppression state will be set to 0 on the database. Contacts delete will initiate the delete process as soon as it is submitted.

In Review ·Reported By 15 ·Updated 2 days ago

Journey Builder Decision Splits in Core Accounts always evaluate preference as TRUE

Marketing Cloud Journey Builder , Marketing Cloud Audience/Contacts

Within Core Accounts using preference attributes set in Email Demographics in Journey Builder decision splits will always evaluate a contact down the "true" decision path.

In Review ·Reported By 2 ·Updated 4 days ago

Contact Data Portability Report is not populated with data in the User Interface

Marketing Cloud Audience/Contacts , Marketing Cloud Reporting

When running the Contact Data Portability Report, the User Interface does not populate the data.

In Review ·Reported By 1 ·Updated 5 days ago

Updated Filter Criteria of Filtered List occasionally is not saved correctly

Marketing Cloud Audience/Contacts

When saving Filtered List Criteria, the updated Filter Criteria occasionally is not saved correctly. This is a very rare issue. * We plan to add safeguards should be added to prevent this from occurring.

In Review ·Reported By 1 ·Updated 9 days ago

Error Generated when Adding record in a Shared DE from a Business unit via the "Add Record" Button

Marketing Cloud Audience/Contacts

When inside of Contact Builder of a BU, and trying to add a single record to a shared Data Extension via the Add Record button, an error is produced. Expected results would be that the record is added successfully, but actual results are simply an error stating: "Review your data and ensure...

In Review ·Reported By 38 ·Updated 16 days ago

Attribute to Attribute comparison does not work when comparing Populations to Event Data

Marketing Cloud Journey Builder , Marketing Cloud Audience/Contacts

Using attribute to attribute comparison between a Population and Journey Data causes all records to go down the same path regardless of meeting or not meeting criteria.

In Review ·Reported By 0 ·Updated 19 days ago

Unable to use Shared/Synced DEs in BUs for AB Self Service Tool

Marketing Cloud Audience/Contacts

When utilising Audience Builder's (AB) Self Service Tool (SST) to implement your own Attributes to create Audiences from, if you select an Attribute from a Data Extension (DE) that is within the Shared or Synced DE Folder, and you're using SST within a Business Unit (BU), the deployment of the Attribute...

In Review ·Reported By 0 ·Updated 20 days ago

Random Data Extension Split fails on duplicate name but does not surface appropriate error

Marketing Cloud Email Studio , Marketing Cloud Audience/Contacts

Random splits can fail to be created when a duplicate name is used. The error is generic and will say "Error: Failed to Create Random Segments".

In Review ·Reported By 0 ·Updated 25 days ago

Unable to modify Data Retention policies on existing data extensions in Contact Builder

Marketing Cloud Email Studio , Marketing Cloud Audience/Contacts

The 'Data Retention Policy' section of the Manage Policies modal was temporarily removed from existing Data Extensions in the Contact Builder application with the 215 Release as a preventative measure related to several potential concerns.

In Review ·Reported By 16 ·Updated 2019-01-22

Data Extensions created with the same external key at both the Enterprise level and BU level cannot be edited.

Marketing Cloud Email Studio , Marketing Cloud Audience/Contacts

Data Extensions with the same name and external key can be created in the shared directory at the Enterprise level, even if the same name and external key exists in a business unit. This results in both data extensions being un-editable.

In Review ·Reported By 1 ·Updated 2019-01-17

1 to 10 of 66 | Next

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.