{"id":44,"date":"2016-05-06T08:56:48","date_gmt":"2016-05-06T08:56:48","guid":{"rendered":"http:\/\/symbioticindia.in\/docu\/?p=44"},"modified":"2016-05-06T08:56:48","modified_gmt":"2016-05-06T08:56:48","slug":"sugar-crm-integration-with-custom-php-applications-i","status":"publish","type":"post","link":"http:\/\/symbioticindia.in\/docu\/2016\/05\/06\/sugar-crm-integration-with-custom-php-applications-i\/","title":{"rendered":"Sugar CRM integration with custom PHP applications (I)"},"content":{"rendered":"\n\n\n
documentation about exposed SOAP functions.
\nThis time the SOAP methods we’re interested in are:<\/span><\/p>\n
    \n
  1. login<\/em>, to log in into sugar crm<\/li>\n
  2. get_entry_list<\/em> to query sugar crm and get lists of Contacts,Accounts etc.<\/li>\n<\/ol>\n

    To access SOAP functionalities from PHP we’ll use the nusoap<\/a> library, which does not require any special PHP extension.
    \nWe’re now going to build a PHP class encapsulating the functionalities we need. In the articles to come we’ll expand this same class with new methods.<\/p>\n

    The code<\/strong>
    \nMost sugar crm SOAP methods require a session id as one of the parameters to make sure we’re authenticated users. We can get a session id by first calling the login<\/em> method.
    \nBut first of all let’s create a basic class with a constructor:<\/p>\n

    <?php
    \nrequire_once(“nusoap.php”);
    \nclass SugarSoap{
    \nvar $proxy;
    \nvar $sess;
    \nfunction SugarSoap($soap_url,$login=true){
    \n$soapclient = new soapclient($soap_url,true);
    \n$this->proxy = $soapclient->getProxy();
    \nif($login) $this->login();
    \n}
    \n}
    \n?>
    \nThe instance variable $sess is the session id we need for most method calls, $proxy is an instance of the soap proxy created by nusoap that allows us to call the required methods.
    \nIn the constructor, $soap_url is http:\/\/mysugar\/soap.php?wsdl<\/em>, changing mysugar<\/em> with the real url of our sugar installation, and $login defaults to true, meaning we want to automatically log in.
    \nWe simply instantiate a soapclient( the ‘true’ as second parameter means we are using a wsdl), get a proxy from it and log in if required.
    \nNow the login method (to be added inside the class). Here it is:<\/p>\n

     <\/p>\n

    function login(){
    \n$params = array(
    \n‘user_name’ => ‘myuser’,
    \n‘password’\u00a0 => md5(‘mypassword’),
    \n‘version’\u00a0\u00a0 => ‘.01′
    \n);
    \n$result = $this->proxy->login($params,’MyApp’);
    \n$this->sess= $result[‘error’][‘number’]==0 ? $result[‘id’] : null;
    \nreturn $this->sess;
    \n}
    \nQuite easy! We use the soap client proxy to call the login method, passing an array containing the parameters it requires. To be more precise:<\/span><\/p>\n

      \n
    1. user_name<\/em> is a valid sugar user<\/li>\n
    2. password<\/em> is her\/his password(note you need to pass it md5 encoded)<\/li>\n
    3. version<\/em> , a version number, not sure it gets checked some way<\/li>\n<\/ol>\n

      The second parameter of the login method is a free string (application name, in the documentation).
      \nNow we have the result of the call in $result, and it’s an array structure. We’ll always have a $result[‘error’] array, and $result[‘error’][‘number’]==0 means no error. If everything has gone fine, we’ll get a valid session id in $result[‘id’], and we save it for future methods calls.<\/p>\n

      <\/span><\/p>\n

      Querying Sugar CRM<\/strong><\/h4>\n

      At this point we have our session id , meaning we’ve been authenticated by sugar crm, and can therefore do some querying. Let’s focus on the get_entry_list<\/em> method. The parameters it needs are:
      \n<\/span><\/p>\n

        \n
      1. session_id<\/em>, what we get after using login()<\/li>\n
      2. module_name<\/em>, that is Contacts,Accounts,Notes,Cases etc<\/li>\n
      3. query<\/em>, a sql like query<\/li>\n
      4. order_by<\/em>, a sql like order by clause<\/li>\n
      5. offset<\/em>, to obtain something like a pagination<\/li>\n
      6. select_fields<\/em>, array of fields to be retrieved<\/li>\n
      7. max_result<\/em>, max number of entries to retrieve<\/li>\n
      8. deleted<\/em>, whether to show deleted entries or not deleted ones (thanks to Mark Clark for spotting an error here)<\/li>\n<\/ol>\n

        So, here is our getContacts method(to be added to SugarSoap class):<\/p>\n

        function getContacts($query=”,$maxnum=0,$orderby=’ contacts.last_name asc’){
        \n$result = $this->proxy->get_entry_list(
        \n$this->sess,
        \n‘Contacts’,
        \n$query,
        \n$orderby,
        \n0,
        \narray(
        \n‘id’,
        \n‘first_name’,
        \n‘last_name’,
        \n‘account_name’,
        \n‘account_id’,
        \n’email1′,
        \n‘phone_work’,
        \n),
        \n$maxnum,
        \nfalse
        \n);
        \nreturn $result;
        \n}<\/p>\n

        The usual call scheme, nothing new. Note the module_name with capital letter.
        \nA note about the fields list: you can get a list of the fields of a module by means of the soap method get_module_fields<\/em>. We’ll see it in the next article, together with the use of custom fields.<\/p>\n

        Managing results<\/strong>
        \nFirst of all, please remember a general rule: if a soap call to sugar crm gives back an empty value(no array), you can be sure there’s a problem with your query or order_by clause. As an advice, always use the notation “module.field”( i.e. “contacts.email1”) when querying. This is I guess because in sugar crm, for any module there’s an additional “_cstm” custom fields table(for “contacts” there’s a “contacts_cstm” table), and fields are taken also from there when querying.
        \nAfter calling our getContacts<\/em> method, the result we get is again an array structure.
        \nHere is an example:<\/p>\n

        Array
        \n(
        \n[result_count] => 3
        \n[next_offset] => 3
        \n[field_list] => Array
        \n(
        \n[0] => Array
        \n(
        \n[name] => id
        \n[type] => id
        \n[label] => ID:
        \n[required] => 0
        \n[options] => Array
        \n(
        \n)
        \n)
        \n[1] ………
        \n)<\/p>\n

        [entry_list] => Array
        \n(
        \n[0] => Array
        \n(
        \n[id] => 83567303-7aad-db69-0d7e-44bde634c3f7
        \n[module_name] => Contacts
        \n[name_value_list] => Array
        \n(
        \n[0] => Array
        \n(
        \n[name] => id
        \n[value] => 83567303-7aad-db69-0d7e-44bde634c3f7
        \n)<\/p>\n

        [1] => Array
        \n(
        \n[name] => first_name
        \n[value] => Mauro
        \n)
        \n[2] => Array
        \n(
        \n[name] => last_name
        \n[value] => Molino
        \n)
        \n[3] ……..
        \n)<\/p>\n

        )
        \n[1] ……..<\/p>\n

        )<\/p>\n

        [error] => Array
        \n(
        \n[number] => 0
        \n[name] => No Error
        \n[description] => No Error
        \n)<\/p>\n

        )
        \nWe’ve already seen the [error] array, [result_count] and [next_offset] are simple, obvious values.
        \n[field_list] contains a multi-dimensional array with data about the fields we have requested, but what really interests us is the [entry_list] array structure. It’s again a multi-dimensional array containing the single records of our search. Every item contains, together with a couple of other fields, a [name_value_list] array , itself containing record data in the form of name\/value pair fields. Now, it is usually more convenient to have these data in the form of a key\/value associative array, so let’s implement the following method, to be put as usual inside our SugarSoap class:<\/p>\n

        function nameValuePairToSimpleArray($array){
        \n$my_array=array();
        \nwhile(list($name,$value)=each($array)){
        \n$my_array[$value[‘name’]]=$value[‘value’];
        \n}
        \nreturn $my_array;
        \n}<\/p>\n

        By passing for instance the [entry_list][0][name_value_list] array to the above method, we’ll get back something like:<\/p>\n

        Array
        \n(
        \n[id] => 83567303-7aad-db69-0d7e-44bde634c3f7
        \n[first_name] => Mauro
        \n[last_name] => Molino
        \n)<\/p>\n

         <\/p>\n

        A little example<\/strong>
        \nWe have now all we need to write down an example. Here it is:<\/p>\n

        require_once “SugarSoap.php”;
        \n$soap=new SugarSoap(‘http:\/\/mysugar\/soap.php?wsdl’); \/\/ we automatically log in
        \n$result=$soap->getContacts(” contacts.email1<>” “,5,” contacts.last_name desc”);
        \nif($result[‘result_count’]>0){
        \nforeach($result[‘entry_list’] as $record){
        \n$array= $soap->nameValuePairToSimpleArray($record[‘name_value_list’]);
        \necho $array[‘first_name’] . ” ” . $array[‘last_name’] . ” – ” . $array[’email1′]. “<br>”;
        \n}
        \n} else {
        \necho “No contacts found”;
        \n}<\/p>\n


        \nWe are retrieving only contacts whose email field is not empty, a maximum of 5 records, order by last name in descending order.
        \nThe foreach<\/em> gives us the retrieved entries as single records that we convert into a more useful associative array structure.
        \nThe visualization is done simply echoing<\/em>. Having the result as a simple array it is quite easy to use it with a templating system like Smarty, to have a nice view of our data.<\/p>\n

        Notes<\/strong>
        \nPlease don’t be too severe with my code quality. To partially justify me, consider I try to go directly to the point, thus ignoring things like error management. I think, but this is only my opinion, that for intermediate\/experienced developers essential code is more readable.<\/p>\n

        Final thoughts<\/strong>
        \nIn this article we’ve seen the basics of sugar crm soap integration, yet we already have something useful to work on.
        \nThe next article will focus on deeper integration between sugar crm and a custom web application; in particular we’ll see how to use sugar crm as an authentication\/user-management system for our web apps, relieving from the burden of implementing it from scratch, while giving us an appealing weapon towards our customers.
        \nPlease don’t hesitate to contact me for any question\/doubt\/advice.<\/p>\n

        Resources<\/strong>
        \n        Sugar CRM integration with custom PHP applications (II) – Using sugar crm as an authentication system<\/a>
        \nThe second article of this series. It focuses on using sugar crm as authentication system and user manager for custom PHP applications.<\/span>        Sugar CRM integration – website session and SOAP session<\/a>
        \nThe third article of this series. It’s about how to use web\/soap session ids\u00a0 in SugarCRM.<\/p>\n

         <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

        documentation about exposed SOAP functions. This time the SOAP methods we’re interested in are: login, to log in into sugar crm get_entry_list to query sugar crm and get lists of Contacts,Accounts etc. To access SOAP functionalities from PHP we’ll use the nusoap library, which does not require any special PHP extension. We’re now going to ..<\/p>\n

        <\/div>\n

        Read more<\/a><\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,2],"tags":[],"class_list":["post-44","post","type-post","status-publish","format-standard","hentry","category-php","category-sugarcrm"],"_links":{"self":[{"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/posts\/44","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/comments?post=44"}],"version-history":[{"count":1,"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/posts\/44\/revisions"}],"predecessor-version":[{"id":45,"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/posts\/44\/revisions\/45"}],"wp:attachment":[{"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/media?parent=44"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/categories?post=44"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/symbioticindia.in\/docu\/wp-json\/wp\/v2\/tags?post=44"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}