You need to sign in to do that
Don't have an account?
Partner WSDL Vs Enterprise WSDL
We are a technology implementation partner of Salesforce and venturing in to our implementation. Is it better to use partner.wsdl vs our client's wsdl (Even if you are developing for just one client.) The documentation mentioned that using the partner wsdl is more difficult to use but more flexible.
(we are planning to use the quickstart file as the base to start our implementation. Do you see any problems with that? Does it have any issues working with partner.wsdl)
Also, we are planning to buy another development account to develop all the functionality and test it with our client's account later (So that we don't mess up their data while developing). So, the WSDL of this development account will only contain some custom fields (that we are actually planning to use) Vs all the custom fields in all the areas that our client is using. Any best practices or pointers to help us out?
Thanks Much
Venk
Also, FYI, there is no automatic way to share customizations (custom fields, etc) between accounts. You'll need to do that manually via the setup UI.
Adam,
Thanks for your response.
You mentioned " You cannot use the quickstat as a basis for a partner WSDL-based integration."
Just curious - why is that? If we use enterprise WSDL for a specific customer (the customers enterprise WSDL), can we not use quickstart as the base?
Is there a reason why we should not do this?
Thanks so much for your help.
Venk