Contacts submitted with NULL date or number values in a CloudPage Entry Event for Journey Builder will not inject the records
Last updated 2 days ago ·Reference W-4832842 ·Reported By 4 users
Submitting a NULL date or number value in a Smart Capture form used as a Journey Builder entry event will cause contacts to fail to be injected. The contacts will be added to the data extension with a default date value of 01/01/1900 and/or a default numeric value of 0. However, what is passed to Journey Builder is not in valid format and will fail.
-Go to Contact Builder > Data Extensions
-Create a new Data Extension (DE) and Name it NullableDate
-Make 3 fields Subscriberkey (text, PK), EmailAddress (EmailAddress, nullable), and Date (Date, nullable)
-Go to CloudPages > Create Collection > Name it NullableDate
-Open the Collection > Create > Landing Page
-Give it a name
-Select Content Builder, next
-Select the layout, create
-Drag a Smart Capture block onto the canvas
-Select "Use In Journey Builder"
-Under Data Target select the NullableDate DE
-Select all 3 fields to be used
-Click on the date field, note it is not required by default
-Click Done Editing
-Save and Publish the CloudPage
-Go to Journey Builder > Create from Scratch
-Drag the CloudPage Event onto the canvas
-Select the NullableDate CloudPage and configure it
-Drag a random split onto the canvas, configure it however
-Give the journey a name
-Configure Journey Settings to allow re-entry and use the email from the CloudPage DE
-Save and activate
-Go back to the CloudPage and find your published link
-Open it and submit the form without filling out a date
-Note the record is added to the DE with a date of 01/01/1900
-Note no contact is injected
-Repeat above steps with number instead of date and will see similar behavior.
Make the field required or omit it from the form.
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.