Skip to main content
グループ

Official: TreeSave API

This group is the official discussion forum for customers and partners who are using the TreeSave API which is in GA for Winter '16 It's a forum for customers to provide feedback, requirements and share ideas. Customers may also leverage this group to collaborate with each other on best practices. This group is maintained and moderated by a salesforce.com employee(s). The content received in this group falls under the official Safe Harbor. Please also see our official Salesforce Customer Community Terms of Use

Announcing SOAP API login() Retirement in Summer '27 release

 

Please refer to these articles for more information: 

Release Note: SOAP API login() Retirement 

Release Note: SOAP API login() not available in API version 65.0 onwards

Knowledge Article

0/9000
0/9000

Hi, what URL should I use to POST tree data?

I tried /services/data/v33.0/sobjects/ with POST method with Json data provided in the documentation but I have the following error:

[ {

"errorCode" : "METHOD_NOT_ALLOWED",

"message" : "HTTP Method 'POST' not allowed. Allowed are HEAD,GET"

} ]

I also tried with /services/data/v33.0/sobjects/account but i receive "No such column 'records' on sobject of type Account"

Thanks in advance

2 件のコメント
0/9000

Hello API enthusiasts,

Dreamforce 2024 is approaching, and I am looking for customers and partners who would be excited to share their Salesforce API journey on the Dreamforce stage together with me.  If this is something that excites you, please reach out to me.

Thanks,

Jeremy

0/9000
0/9000
0/9000

Salesforce Platform APIs: Ask Me Anything January 2024

 

Join our experts @Jeremy Westerman and @Kris Harrison hosted by Developer Advocate @Philippe Ozil for the January edition of our Salesforce Developers Ask Me Anything series to get all the details you need to succeed.

 

Date: Wednesday January 31, 2024

Time: 9am PT

Theme: Salesforce APIs

Registration: https://bit.ly/sfdevsamajan2024

Salesforce Platform APIs: Ask Me Anything January 2024 Join our experts and hosted by Developer Advocate for the January edition of our Salesforce Developers Ask Me Anything series to get all the deta #API #Platform Developer #Salesforce Platform

 

@Official: Bulk API 2.0 @Official: Composite API @Official: TreeSave API @OpenAPI Specs for Salesforce REST APIs @* Salesforce Platform *

0/9000

Relating to master/detail updates, can you give any more detail about the error response [{"message":"Nested object for polymorphic foreign key must have an attributes field before any other fields.","errorCode":"JSON_PARSER_ERROR"}]"?

I can insert a nested records array with a single detail object just fine, but when I add two (with separate refs in the attributes map), I get the error above.

9 件のコメント
  1. 2015年12月23日 17:04
    Yes, this is fixed in Winter '16, so you should be able to test it out right now.
0/9000

Hi, I was trying to create parent and child records using SObject Tree REST API but when the JSON request contains 2 duplicate child records, it throws a generic exception as below.

 

ERROR:

UNKNOWN_EXCEPTION message: An unexpected error occurred. Please include this ErrorId if you contact support: 810374692-4687 (173351053) errorCode: UNKNOWN_EXCEPTION

 

Even after throwing the exception, records are getting created in Salesforce. An external application is calling this API to create orders in Salesforce.

0/9000
Are there any examples of how to use the Tree API to insert child lookup objects? The examples don't show any, but the docs (https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/requests_composite_sobject_tree.htm#topic-title

) make it seem as if it's possible: "Child relationships are either master-detail or lookup relationships"

Thus far I'm getting various errors and sometimes exceptions, so I wonder if you could show an example with JSON, or give more info on how to specify a lookup that is not master-detail?

the docs

4 件のコメント
  1. 2015年7月2日 17:33
    Jay -- Thanks for that. It's too bad there isn't a way to create lookup objects inline with assigning them to the lookup fields, since I think that'd fit naturally with the Tree API. I understand it isn't in your current design, but hopefully it will come one day.
0/9000