E2.0 Child BU - Automation Studio Type Audience will cause error if using Data Extension with CustomerKey used by other DE in E2.0 Account
Last updated 2019-12-02 ·Reference W-4336553 ·Reported By 2 users
Issue occurs only in Business Units other than top-level of Enterprise 2.0 account.
Issue occurs only with Automation Studio type Audience.
If the Automation Studio Audience is configured for a Data Extension whose CustomerKey value is used by a Data Extension in another Business Unit in the E2.0 structure, it is possible for an error to occur which prevents the Journey from being saved or activated. This typically occurs if the Data Extension's CustomerKey is used by another Data Extension in the top-level Business Unit.
The error displayed in the user interface is:
"Data Extension 00000000-0000-0000-0000-000000000000 must exist and be active"
During configuration of the Automation Studio Audience Entry Source, once the Data Extension is selected, record count from the Data Extension is displayed. When this issue occurs, that record count is not derived from the Data Extension in the Business Unit where the Automation exists.
1- Access enterprise 2.0 account's top-level MID
2- Navigate to Email Studio - Subscribers - Data Extensions
3- Create a Sendable Data Extension with Customer Key equal to "BU-External"
4- Navigate to Audience Builder - Contact Builder - Data Extensions
5- Click into the DE created in step 3 and select the Records tab
6- Add two rows to the Data Extension
7- Change to a Business Unit in that E2.0 account
8- Navigate to Email Studio - Subscribers - Data Extensions
9- Create a Sendable Data Extension with Customer Key equal to "BU-External"
10- Create a copy of the Data Extension, Customer Key does not matter
11- Navigate to Audience Builder - Contact Builder - Data Extensions
12- Click into the DE created in step 10 and select the Records tab
13- Add one row, or more than two rows, to the Data Extension
14- Navigate to Automation Studio - Automation Studio - Activities
15- Click the Create Activity button
16- Select the SQL Query option
17- Use SQL so that all rows from the DE created in step 10 are selected
18- Click next and then select the DE from step 9 as the destination using the Overwrite option
19- Click the Finish button
20- Navigate to Automation Studio's Overview tab an create a new Automation
21- Use the Schedule type Starting Source and drag SQL Query type Activity to the canvas
22- Using the "Choose" button on the SQL Query Activity, select the Query Activity created in step 19
23- Save and close the Automation
24- Use the "Run Once" option for the new Automation
25- Ensure that the rows created in step 13 appear in the DE created in step 9
26- Navigate to Automation Studio - Journey Builder in that same BU
27- Create a new Journey
28- Provide a name for the Journey
29- Drag an Audience type Entry Source to the canvas and click the Configure button
30- Select "Automation Studio Audience" option and click next
31- Complete Properties step and click next
32- Select the Automation configured in step 23 and click next
33- Select the Data Extension created in step 9
34- Observe the number in the "Records" section is 2 instead of the expected rowcount per step 13
35- Click next, configure an entry schedule and click next again, then click Done on the summary screen
36- Click the Save button, observe error "Data Extension 00000000-0000-0000-0000-000000000000 must exist and be active"
Do not use the same CustomerKey for Data Extensions existing in different Business Units of an Enterprise 2.0 account.
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.