sugarondrupal.drtsg.net

With the goal of provide support for versions 1 and 2 of the SugarCRM WebServices, I had to do a triage of 'functionality' to be provided by them. I've listed and sorted the API functions included in SugarCRM 5.2 and 5.5 versions, for the versions 1 and 2 of the Web Services. There are a lot of missing methods (they where documented as deprecated, or superseed by another), and there are new ones.

I've included two pics with the results:

• SugarCRM_WebServices_set_1.png: is the selected API set to be managed by SugarOnDrupal modules. Well, actually, a wrapper should be done to take care of missing or changed APIs, but the API set is more or less clear.
• SugarCRM_WebServices_set_2.png: includes a list of API I guess I will try to avoid. I'm not sure if all the functionalities will be achieved without any of the API methods included in this list, but I'll try.

The next move is to make sure that the "selected API set" could really be used to manage all the functionalities, wrap them into a single calling object, and cross the fingers :) Let me explain: a request in version 1 and version2 would probably have different arguments, in number and types, but also, the service response would be different, including more or less information.

Just to make an introduction I will list two quick examples I've found:

• In V1, each get_entry or get_entry_list request returned a "field_list" array, containing the description of the fields returned. This has completely dissapeared in V2 for now (I don't know if it will be included), and now we have a new "relationship_list" array, with additional information.
• In V1, leaving empty the parameter 'field_list' would make the call return ALL the available fields for the requested bean. Now, in V2, it is necessary to specify the fields you want to get, or just would get only the SugarBean IDs in the reply, and no additional fields.

I hope I could complete this information quickly, to be able to set the Drupal to SugarCRM conversation flow ASAP!.