You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From Bstack:
Currently the put/post/patch for contacts all don't have createTimestamp on them which we need in order to decide which source to put in the column at insert-time. We can kinda ignore it in the post but not so much in the others, especially problematic in put afaict.
Would it make more sense to you two for me to breaking-change that into the schema, continue trying to find a workaround, or make a stab at the "figure it out from the newsletters table at get time approach
Request from MoCo marketing and MoFo.
From Bstack:
Currently the put/post/patch for contacts all don't have createTimestamp on them which we need in order to decide which source to put in the column at insert-time. We can kinda ignore it in the post but not so much in the others, especially problematic in put afaict.
Would it make more sense to you two for me to breaking-change that into the schema, continue trying to find a workaround, or make a stab at the "figure it out from the newsletters table at get time approach
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: