Triggers are not firing when a record is queried, but formula fields are recalculated. This error is normally happening, if the SOQL query to get record information, exceeds the character limit of 20K.
I can make an assumption, that the Account object has a big number of custom fields (more than 250) and some of them can be pretty complicated formula fields.
Actually, as of Sept. 2021, it turns out you can.
Salesforce's documentation isn't very clear on this. You can't edit the update reminder entries themselves, but you CAN turn update reminders on and off.
The relevant settings are in settings/Opportunity.settings-meta.xml:
A successful update is a 204 response. That status code means "your operation was successful, and there is no response body." If there were an error, you'd get a 4xx or 5xx status code with a response describing the error. If you want a fresh copy of the data, you will need to retrieve it somehow, such as using a GET call, or using a composite REST ...
Currently, as per this document, the API version supported since the June 2021 release, is v51. Below is copied from the release notes:
Marketing Cloud Connect API v51 Upgrade
Journey Builder Integrations and Synchronized Data Extensions now support the latest API version 51, unlocking access to Loyalty Management and Order Management objects for use as the ...
Typos in the documentation are rare, but they do happen. While some salesforce.com employees are members of this forum, this is not an official channel for reporting these kinds of problems. You can use the Feedback tool to report problems, or you can contact the Documentation Team on Twitter, and they'll log an issue to have it fixed.
As mentioned by Adam Spriggs, JourneyBuilder is using the REST API and is not addressable via SOAP.
The object you are referring to are not related to the current JoruneyBuilder object in Marketing Cloud. As you can see in the SOAP Supported Operations For Objects And Methods neither InteractionBaseObject nor InteractionDefinition is listed at all.
All this is quite well-described in the documentation. You can define a number of attributes in the payload, which can hold additional information for your journey. In below example, two attributes are added: one holding the URL, another holding the full name.
In case it helps anyone who has the same problem: I had a similiar situation in my org today, and I found out that the object has a before insert trigger which changes the value of the external id field.
I was doing a Patch rest api with "external_id__c" = "example1", and in the before insert trigger, apex changed the value external_id__c ...
SFMC REST API calls only have a single function -- hence the variety of endpoints available for interacting.
If you need additional personalization data for your email, you'll need to:
pass it in the API call as a separate attribute/payload or
use a separate call in your integration for the supplemental data.
The first option way more common, due to the ...
That package is for Salesforce Core and not for Salesforce Marketing Cloud (SFMC). Salesforce Marketing cloud has its own authentication system as well as different API capabilities and endpoints. This means that nothing in that package will interact or authenticate inside SFMC.
I do not know of anything that is not a paid service that allows you to interact ...
The documentation doesnt mention header parameters for GET - but the HTTP GET AMPscript requests do support it if we pass the header name and value pairs as parameters in the function call.
I have shown the same in the video example as well - guess we need the SFMC documentation to be updated
FWIW, I did the following experiment:
Did some API requests up to 16:15
Stopped doing any requests for 24h
Usage was down to zero at 16:00 next day.
So it looks like it keeps track of how many calls were made each hour and forgets about hour T-24 as soon as hour T-0 begins.