Greetings,
We have activated Contact-to-Account feature (switch) according to the guide here
In the guide, there are a number of restrictions mentioned. But I haven't seen any related to forms/landing pages?
We're using forms/landing pages in S...
Greetings,
We have a business requirement where business users need to maintain multiple values for an information that should be related to campaigns.
As far as I know, extension fields/objects I create for campaign business object, it's not pos...
Greetings,
We're trying to establish the connection between SAP Marketing and GoTo Webinar. We just copied standard integration CPI package named Third Party Marketing Events Integration with SAP Marketing Cloud and SAP Marketing
We're trying to ...
This blog is successor to this blog. So I highly recommend you to read it first before proceeding with this one especially if you don't know the meanings of the notations (Message A, Message B etc) that we use in this blog. The predecessor blog expla...
Introduction
In this blog, we're going to learn how to extend SAP Marketing integration flows by using post-exits.
It's quite common that you require custom (extension) fields (specific information regarding your business needs) in your integration ...
Hello eliocentenob , Sorry for the late response. For availability of standard fields for OData API's, you can quickly check metadata information for related OData API. For instance, for API_MKT_CONTACT_SRV, you can check the XML file for the reponse...
Hi christopherlinke ,
Good. Personally, I just compare "Message B" in upgraded standard iFlow with "Message B" in Post-Exit. If there is no difference, I then check the endpoints of SOAP services and OData versions for Message A and Message C just t...
Dear community,
I updated the blog with an important explanation like below for the section -> 2.5. Performing Post-Exit Mapping
"!!!CAUTION!!!: You should really be careful when performing post-exit mapping here. Kindly note that, the messages her...
