A newly created transactional send on Child BU uses wrong sendlog DE when Enterprise Sendlog has been deleted
Last updated Yesterday ·Reference W-10178510 ·Reported By 1 users
A Child Business Unit is set up to use the SendLog DE within the Top Level Enterprise Business Unit
The Enterprise level SendLog is deleted and a new Child BU level SendLog is created.
If a new triggered send is created it will use the Child BU Send Log. However when a Transactional Send is created this will continue to try and use the deleted SendLog DE.
> Child BU is set to log to the Enterprise Level SendLog DE
> On the Enterprise level, navigate to the Data Extensions and delete the SendLog DE
> Make sure there is one active SendLog DE at the BU level
> Create a new Transactional Send via Rest api
> Sends via the new Transactional Send will not be logged.
Note: Creating a new Triggered Send through the UI does not encounter the same problem and will fall back to the Child BU SendLog DE
Contact Marketing Cloud Support who can change the Child BU to use the SendLog DE located in that BU instead.
Reported By (1)
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.