Best practice for creating Datastreams per development environment | Community
Skip to main content
yuhuisg
New Participant
August 5, 2022
Solved

Best practice for creating Datastreams per development environment

What's the best practice now for creating Datastreams in relation to the development environment (i.e. development, staging, production)?

I remember that when Datastreams were first introduced, creating a single datastream would result in 3 datastreams, 1 for each development environment. All 3 datastreams retained the same datastream ID, though the development and staging ones had ":dev" and ":stage" appended to their IDs respectively.

But now, when I create a datastream, I end up with just 1 datastream. Does this mean the best practice now is to create separate datastreams -- that end up with different datastream IDs -- for each development environment?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
caitlincodyAccepted solution
Employee
August 19, 2022

Datastreams are sandbox aware now, so it can match your AEP sandbox environments.

At a minimum 1 prod and 1 non-prod Datastream

1 reply

caitlincodyAccepted solution
Employee
August 19, 2022

Datastreams are sandbox aware now, so it can match your AEP sandbox environments.

At a minimum 1 prod and 1 non-prod Datastream

Translate