You need to sign in to do that
Don't have an account?
Tran Man
PHP Toolkit v11
The PHP toolkit provides you an easy way to make Web service API method calls.
Newly supported or enhanced in this release are:
* Metadata API
* Email
* Merge
* Workflow
* EmptyRecycleBin
* Proxy Server
* LoginScopeHeader
* Header Options at the Connection Level
Click this link to enjoy. Be sure to check out the extensive Samples section as well.
I wonder if you could clarify the status of this (and other) toolkits within SFDC. As you can appreciate - there was quite a significant delay between your Dreamforce demo and annoucement "within the week" and availability of this toolkit.
I asked our premium support rep and got this response:
"unfortunately the tool kits are not supported products, as per our main application. We are unable to give specific dates on releases of new updates. I do have an email in to the developer team to see if they can provide any further insight."
Which then leads us to question the specific toolkits or use of APIs with our SFDC implementation. I would love you to clarify SFDC's position on this.
Thanks,
PG
Given the popularity of PHP and the fact we use the PHP toolkit quite extensively internally, we will continue to maintain and update it. On another note, I know of several developers that went ahead and extended the toolkit with new API calls and other functionalities which we were happy to see. We are looking to make community contributed code easier in the future.
Hope that helps.
This code seems to have gone away - there's no mention of setClientId in the code anymore. Instead of doing this, do we now just create an Enterprise client object and skip the setClientId step? Are there any other steps to upgrading or is everything pretty much backwards-compatible? (There just seems to be a lack of detail about an upgrade path)
Although you can technically do it, it doesn't make sense to set a Client ID on an enterprise wsdl connection. If you're developering a partner app, you should be using the partner wsdl.
Here is a code sample for CallOptions which supercedes the setClientId method in the old toolkit. Let me know if it works for you so that i can post it. The first argument to CallOptions is a Client and hte second is a namespace prefix for managed packages. Both are optional.
Also, what should be put for aNamespace? Does this value get validated?
e.g. you have a managed package with a namespace of foo, and you have custom fields on account of foo_bar, foo_baz, and foo_quartz. If you set the namespace header to "foo", you can use bar,baz,quartz as the field names in your API calls (e.g. in a SOQL query, or an update call).