New answers tagged

2

Every API call to salesforce will count towards your limit. You can consider upgrading to a higher-tier edition of salesforce or buying more licenses in order to increase your limit but there's always a limit. You'll likely want to consider a different integration architecture altogether if you wish to reduce your calls somehow. Some ideas off the top of my ...


2

Generally speaking, you have two options. The first option is to set up a server on localhost, and listen for a connection from the browser at the end of the flow. This is often something like https://localhost:1717/oauth/success. This is how the Salesforce DX CLI operates. The second option is to listen to a WebView or similar component for when you land on ...


4

Yes, you're allowed to upsert against a Salesforce ID. You can read more about this in the various documentations, such as REST and SOAP. In fact, in some objects, you can even use the Name field, as long as the idLookup property is true for that field. In fact, the documentation even calls this out explicitly: This example uses the POST method as a special ...


1

Deployments are locked serially, along with any changes an administrator may be performing. As such, you can't particularly guarantee that the system will be able to complete even a single deployment of a single field within the two minute timeout. You need an asynchronous solution if you're going to stay in Apex. Technically, this is a very interesting case ...


1

The problem was in my dataset.zip. I changed the following things, without trying out what the significant change was: changed labels (foldernames) from numbers to letters, starting with a capital letter removed "_" from the image filename smaller dataset


0

You can use this API and take a look at the EPT metrics (Experienced Page Time) for your page.


1

Like the error you're getting says, you can't have a string literal (text enclosed inside of single quotes 'like this') span multiple lines. Bad: String myStr = 'Haikus are easy but sometimes don\'t make much sense refridgerator'; If you need to have a multiline string (if for nothing but keeping things organized and easy to read), then you need to have a ...


0

Feature licenses cannot be queried or pulled using API at this time. There is an idea around this today Usage-Based Entitlements can be queried with the help of below query: SELECT AmountUsed,CurrentAmountAllowed,Frequency,IsPersistentResource,UsageDate FROM TenantUsageEntitlement NOTE: We cannot query the Name field from TenantUsageEntitlement object. It ...


0

The documentation for UserLicense does not have an expiration date field to be retrieved using API so unfortunately, it is not possible to retrieve using API. This information is not exposed under API or Apex. But it is available on the user license related list on the company information page. If something is not exposed in api, but available on set up page ...


0

As per Connect:Direct documentation, there is no support for any FTP-like protocol within IBM Sterling Connect:Direct, making it unsuitable for providing data to SFMC (as the only supported protocols for file transfers are SFTP/FTPS). You will need to utilise some sort of middleware, to either connect to the Marketing Cloud APIs or SFTP.


0

Looks like you had conflicting namespaces and was causing a 'Bad Request' error, hence the 404. You were using s: and a: in your header tag instead of the declared SOAP-ENV: and xsd: that you had in the envelope. Once this was altered, it worked as expected. See below working example from your code: <?xml version="1.0" encoding="UTF-8"...


2

You need to parse the JSON response and select the value that you are looking to populate. You can do this fairly easily with SSJS: <script runat="server"> Platform.Load("Core", "1"); /* GET HTTPGET RESPONSE */ var jsonResp = Platform.Function.ParseJSON(Platform.Variable.GetValue("@shortenUrl")); /* GET SHORT ...


0

Thanks for posting the original code snippet and I understand the need to use a JWT flow instead of the other proposed options. I was able to make one small change to what you had and got this working as expected. The main problem you were facing is how the signature was encoded. Notice that I added a little extra to the base64 encoding for the secret. This ...


0

When there is an encoding issue, Salesforce will not be able to understand the assertion and will respond with {'error_description':'invalid assertion','error':'invalid_grant'}. As per the documentation, when posted to the token endpoint, the assertion must be encoded using base64url encoding as defined here: http://tools.ietf.org/html/rfc4648#page-7 I have ...


Top 50 recent answers are included