It's that time of year again! No, not Thanksgiving, Black Friday, holiday preparations, etc. I'm talking about Sitecore MVP application time!

In my last post I covered sending data to a Send email list, and my last comment was about making sure Authors don't have to jump through hoops to get its Guid. In this post I'll share making this selection a custom field in Content Editor. 

I recently built a helper method for our Send gateway which adds or resubscribe users to specified lists. I reported a bug since resubscribing Users kept reverting to unsubscribed. I'll cover the workaround and the explanation from Send for this behaviour. 

Ok, that's it! We're in the final piece of this four-part series for the Send to CDP Sync module. In this episode, we will cover the API calls used for deploying the batch file, monitoring its progress and securing the local cache which was covered in the last post.

So far, we've covered the Send to CDP module's introduction, getting data from Send and preparing a list of guests for upload. Since there's a hard limit of 50mb per upload I wanted to use a local cache so only changes are sent on each iteration. We'll go over that in this post.

In my first post I introduced you to the Sitecore to CDP module, which will create a structured extension with all Send email lists and if the Guest subscribed to them. In this post I'll walk through the process of getting all data out of chosen Send lists so they can be sent to CDP as a batch file.

What if you wanted to instantly see all Send email lists your CDP Guests are subscribed to? This module will collect information from Send and populate CDP with what they've signed up for. It also maintains the last updated timestamps for each list preference and deploys the changes in batch files. Uploads are minimal by using a local cache, and the preferences are structured in a single extension.

If you saw my post yesterday about adding a preview link to sites, you might come to the conclusion that I've added a 2^nd publishing target. Works great, but if publishable dates are set, nothing will get published to this new preview target. I've created a simple processor to handle this.

It's never come up before since I didn't have the need, but we recently added a 2^nd publishing target to a site that was a private Content Delivery instance used for preview for non-Sitecore Users. While doing this I wanted to add the preview link in the Content Editor, so this change allows for that.

A team member came to me this week with an exception I haven't seen before, which was “Too many variables in the testset”. Searching online was fruitless, so I wanted to share the reason and workaround for this bug.