Setting meeting attendee status over SOAP

[usiw]

We are using the SugarCMR v4 soap interface (/service/v4/soap.php) to sync between Sugar and our messaging server. One of the limitations of the soap functionality is that it doesn't appear that we can set extra fields contained within a many-to-many relationship table. The most prevalent example is the meetings_users, meetings_leads, and meetings_contacts tables with the required and accept_status fields.

Is there a way with the v2,3, or 4 SOAP functions to set the fields? I did try the name_value_list array on the set_relationship function but that didn't work, and the Developers Documentation on the Sugar website is severely lacking when it comes to SOAP and REST.

[christianknoll]

Look at our KINAMU Outlook Connector (you will find it on SugarForge) there is also a soap extension we have written that provides that functionality.

We are using the SugarCMR v4 soap interface (/service/v4/soap.php) to sync between Sugar and our messaging server. One of the limitations of the soap functionality is that it doesn't appear that we can set extra fields contained within a many-to-many relationship table. The most prevalent example is the meetings_users, meetings_leads, and meetings_contacts tables with the required and accept_status fields.

Is there a way with the v2,3, or 4 SOAP functions to set the fields? I did try the name_value_list array on the set_relationship function but that didn't work, and the Developers Documentation on the Sugar website is severely lacking when it comes to SOAP and REST.

[usiw]

We aren;t looking at having an Outlook plugin since they are difficult to manage(install, update, permission) for all of our sales reps. We currently integrate directly with Exchange through EWS and plan to connect with other third-party messaging servers in the future.

With that being said, I prefer not to modify the core codebase of Sugar, which the extension that you mentioned does by overwriting the soap/SoapSugarUsers.php file. We prefer to have as much done in custom modules or withing the /custom folder as possible since we tend to keep our Sugar Pro instances as current as possible.

Is there something I am missing in the Soap API, or is this a "feature request"?


Side note - I noticed that soap.php is radically different than services/vn/soap.php in terms of functionality (and bugs). Some of the soap functions have parameters that aren't even reference in the code! Sugar should clean up their API with a v5 release that is a complete rewrite. v4 was also supposed to be .NET compatible but it failes miserably when it comes to soap faults (simple fix is to reverse two lines in nusoap fault code).

[usiw]

The KINAMU Soap extension you mentioned is also poorly coded. None of the SQL queries are properly escaped and they use query instead of pQuery. Many of the parameters also don't make sense. For example, get_relationship_activity has a $related_module parameter that does nothing. The code uses it to get a bean instance of that module jut to get the db parameter when $GLOBALS['db'] would work just as well. I could also pass any valid module name and get the same results (eg, Projects, Cases, etc) even though they are unrelated to the meeting. It appears that the code base suffers the same annoyances as the Sugar code base.

Overall there is some good functionality that I would like to see make it's way into core sugar, especially when (if) Sugar does a calendar rewrite!

[christianknoll]

In any case it works and fixes the problems you are looking at. So feel free to use it or to code it yourself.

In the spirit of open source you could fix it.

christian.

The KINAMU Soap extension you mentioned is also poorly coded. None of the SQL queries are properly escaped and they use query instead of pQuery. Many of the parameters also don't make sense. For example, get_relationship_activity has a $related_module parameter that does nothing. The code uses it to get a bean instance of that module jut to get the db parameter when $GLOBALS['db'] would work just as well. I could also pass any valid module name and get the same results (eg, Projects, Cases, etc) even though they are unrelated to the meeting. It appears that the code base suffers the same annoyances as the Sugar code base.

Overall there is some good functionality that I would like to see make it's way into core sugar, especially when (if) Sugar does a calendar rewrite!