New answers tagged api
1
You need to include the namespace:
const columns=[{label: 'Id', fieldName: 'Id'},{label: 'Field API Name',fieldName: 'bhdata__Field_API_Name__c'},{label:'Object API Name',fieldName:'bhdata__Object_API_Name__c'}];
1
You'd need to first GET all your locations from the /push/v1/location REST route. And then, either update your existing message using PUT /push/v1/message/{messageId} and passing in your array of Location IDs returned in your GET to the geofences property of your PUT request or create a new message from scratch using POST /push/v1/message.
1
This got worked by removing the CURLOPT_HEADER option.
curl_setopt($ch, CURLOPT_HEADER, 1); //remove
0
Even though this question is one year old I had the same issue today and found a solution to that problem.
With standard Rest API, your request only needs a slight modification:
{
"FinServ__Account__r":{
"External_Id__c":"account-external-id-1"
},
"FinServ__Message__c":"Alert-Subject-Finserv-CREATE-1",
"...
3
Given your comments, use JavaScript to make the API calls. You can call a wire method, precisely wait at least 101 ms (or any other value), then continue. As a practical example:
createPrimaryAccountAndContact({data:data})
.then(result => new Promise((resolve, reject) => setTimeout(resolve, 101)))
.then(result => createContact({data:data2}));
You'...
0
You only need to create one definition per message template. Each send would then use that definition. So you're not creating a new definition for every single contact.
I believe the example for transactional SMS is using a payload for the generic SMS triggered send as the parameter isn't listed in the documentation. It shouldn't be required for ...
1
It looks like the client was using the legacy API package. There is a V2 that has different parameter/naming convention in order to get a token. V2 Access Token
0
Hi you missed this keyword before the properties firstname and lastname since in the connectedCallback() the two are treated as different properties. So in order to access the global properties defined above use this.firstName+ ''+ this.lastName.
0
Short Answer:
Yes this is possible...but you probably shouldn't do it that way.
Long Answer:
I would highly recommend not going this way. Having the entire email passed inside of an API call is a lot of information that needs to be sent, received and processed for each email. With any decent type of volume/frequency, you are looking at potential for your ...
4
You need to use this to access member attributes.
this.fullName = this.firstName + " " + this.lastName;
Note also that neither variable will be available in connectedCallback(), as the data is loaded asynchronously. Use this instead:
get fullName() {
return `${this.firstName} ${this.lastName}`;
}
I made a Playground that demonstrates this idea. ...
2
This code won't work because you have a syntax error in your SOQL query:
List<Campaign>campaignlist= New List<Campaign>([selectid,Campaign_ID__c,Clicks_Interactions__c,Impression__c,Conversion_rate__c,Conversions__c,Cost__c,Cost_per_conversion__c,CTR_Interaction_rate__c from Campaign where Campaign_ID__c!=null]);
selectid should be SELECT Id.
...
2
The composite tree resource always creates new records, which is why it gives you that behavior. Instead, you'd use a composite request. This example gives you the closest behavior you have available. You'd start by using a GET /services/data/v48.0/sobjects/Account/External_Id__c/x165, which returns the account, then use that reference in further updates.
...
3
An API user can be used across multiple sessions, and Connected Apps can be used for multiple purposes, but you'll need to keep in mind that there are a few limits.
Connected Apps can only have five sessions per user, so using separate Connected Apps will reduce the possibility of sessions expiring early. This can cause erratic app behavior.
Users can only ...
3
Yes, you can re-purpose it.
Best practice is that each client (App A vs App B) has its own connected app. With 2 connected apps (1 per client), you can still use the same user account to authorize access to the app...but each client will have its own set of credentials (consumer key + secret). Why 2 apps vs 1? Consider a scenario where at some point in the ...
0
I will do it this way.
Create a class to wrap your JSON:
public class WrapperRequest {
public GetAircraftListResult getAircraftListResult;
public class GetAircraftListResult {
public String responseid;
public String responsestatus;
public Integer count;
public String pagelink;
public List<Aircraft> aircraft;
}
public class ...
0
Just map it so you have a List<Aircraft as one of your properties.
public class Payload
{
Result getAircraftResult;
public class Result
{
String responseId, responseStatus, pageLink;
Integer count;
List<Aircraft> aircraft;
}
public class Aircraft
{
Integer aircraftid;
// etc
}
}
...
0
The parts in the array need to be in a list:
public class Aircraft {
public String aircraftid;
public String make;
// ... //
}
public class AircraftListResult {
public String responseId;
public String responsestatus;
// ... //
public List<Aircraft> aircraft;
}
1
Here is the configuration I have to have Salesforce 2 calling Salesforce 1 API:
In Salesforce 2: Named Credentials
Certificate: using one created from Salesforce 2 (Certificates and Key Management)
Identity Type: Per User
Authentication Protocol: JWT Token Exchange
Token Endpoint URL: https://login.salesforce.com/services/oauth2/token
Scope: api web ...
3
Your best bet is to use the APIs to collect this information. Do note though that this will be at a per BU level and not an enterprise level, so you may need to do each of these multiple times to get all across each BU. You also need to verify that your count is not greater than the max page size. If so, you will need to do multiple calls to ensure you get ...
1
To upload files larger than six megabytes, you could use the AJAX Proxy in Visualforce. This will require re-implementing your logic in mostly JavaScript. However, unlike Apex, it has an unlimited payload size (I've tested over 100MB with this), so it should be able to handle whatever you want to throw at it.
0
The issue was due to the fact that the characters in the JavaScript were getting escaped, hence the form was not displaying / submitting properly.
Example
if (!popupWin || popupWin.closed) {
should have been
if (!popupWin || popupWin.closed) {
After just replacing the escaped characters in the JS part, form was submitted properly.
3
There is no automatic way to listen to imports/updates to a Data Extension. If you import a CSV a file drop automation could be suitable, otherwise you will need to trigger the API using a program/code. However, check if a realtime trigger is really necessary for your use case or a data extension entry source with a recurring schedule is also sufficient.
...
0
It appears that status is not available as an overall return as you have it with json.status. status is instead on a per object basis inside the results array on each individual object.
So would have to be returned via json.results[0].status to get status on first call and so on. Perhaps this is what is causing the error?
0
I believe you are missing the 'keys' node for this envelope:
<Keys>
<Key>
<Name>Subscriberkey</Name>
<Value>mySubkeyValue</Value>
</Key>
</Keys>
Which should be above the 'Properties' node like so:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="...
1
You can of course use Salesforce's full selection of APIs to call for Salesforce data from off-platform.
The direct equivalent of Lightning Data Service, when called from off-platform, is the User Interface API. This is in fact what directly powers Lightning Data Service.
https://developer.salesforce.com/docs/atlas.en-us.uiapi.meta/uiapi/
0
Lightning Data Service is currently only available when building on the Lightning Platform.
Check out https://www.salesforce.com/video/7810759/ for some hints on the roadmap #SafeHarbor
1
Moved to answer from comments for better visibility:
I believe the issue is with your headerNames and headerValues variables.
These cannot be arrays. If you have multiple headers/values to place, you would do multiple setHeader actions.
E.g.
req.setHeader('header1','header1Val');
req.setHeader('header2','header2Val);
Top 50 recent answers are included
