Katja_Keesom

I would recommend clicking through to the links Sanford provided in his post. There is very detailed information there about what is and is not possible, your developers should be able to work off that easily. In addition, I find this section of the developer documentation also useful: https://devel...

@Jo_Pitts1 is right, we need a bit more to help troubleshoot.One tip when copying and pasting to avoid the tons of code is never to copy and paste directly, but either go through Notepad first to strip the styling, or paste using ctrl-shift-v (in Chrome) in order to strip the styling.

Normally, a person is assigned to the default partition associated with the workspace your form is created in. As @SanfordWhiteman indicated, you can reassign quite simply using a smart campaign flow step (assuming the smart campaign is in a workspace that has access to the partition involved).

Normally, when you export the members of a list, the pop up will show a hyperlink to download the file. The screenshot already gives you a great hint though. It says "No ECIDs were exported.", so what you were trying to export contained no members and therefore there was nothing to download.As @Sanf...

In addition to @Michael_Florin 's confirmation, I would actually leave the person in the stream they are in and simpy change the cadence. If you move them to a "paused stream" (I presume you would intend to create a stream without content or something along those lines), you lose the valuable inform...

Last silly check: Both reports have the same time reference set?

It might be worth checking the campaign queue as well to see whether there's any processes running that slow the platform down.

Hi @Shane_Rourke2 , the default value for the cadence is Normal, so as soon as you add a person to an Engagement Program that is what they will be set to. There's a plethora of reasons why you could afterwards want to pause them, so they stop receiving the content. A simple example would be they do ...

I haven't seen the S2S solution in action yet, so cannot tell you at this stage. Also not sure who were in the beta, so can't refer you either I'm afraid. We'll have to see when it goes live.

Hi @Shannon_Kelly1 ,What I know of the new S2S connection is that it would not use a sync user anymore, so there would also not be a username and password, only client id and client secret. That means that MFA has no impact anymore, as that is related to the sync user.I know the method has been test...