-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] creating events fails if deKey is set alongside schema #1406
Closed
1 task done
Milestone
Comments
JoernBerkefeld
added a commit
that referenced
this issue
Jul 5, 2024
JoernBerkefeld
added a commit
that referenced
this issue
Jul 5, 2024
4 tasks
JoernBerkefeld
added a commit
that referenced
this issue
Jul 5, 2024
JoernBerkefeld
added a commit
that referenced
this issue
Jul 5, 2024
4 tasks
JoernBerkefeld
added a commit
that referenced
this issue
Jul 8, 2024
JoernBerkefeld
added a commit
that referenced
this issue
Jul 8, 2024
JoernBerkefeld
added a commit
that referenced
this issue
Jul 8, 2024
JoernBerkefeld
added a commit
that referenced
this issue
Jul 8, 2024
JoernBerkefeld
added a commit
that referenced
this issue
Jul 8, 2024
Closed by #1417. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
in our scenario, schema does NOT have a de-key set but the generic de-key is set outside of the schema.
pre-deploy steps look for the dataExtension and because we are trying to create the API event, that DE also doesn't exist
Expected Behavior
we want SFMC to auto-create it for us based on the schema.
for that, the schema needs to have the DE key set so that it knows how to name the DE.
also, the preDeploy step needs to accept that it cant find the DE for CREATE only
Version
7.0.3
The text was updated successfully, but these errors were encountered: