{"id":770,"date":"2020-05-16T05:18:14","date_gmt":"2020-05-16T05:18:14","guid":{"rendered":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/?post_type=lsvr_kba&p=770"},"modified":"2020-05-16T05:37:51","modified_gmt":"2020-05-16T05:37:51","slug":"zoho-api-name-notation-change","status":"publish","type":"lsvr_kba","link":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/knowledge-base\/zoho-api-name-notation-change\/","title":{"rendered":"Zoho API Name Notation Change"},"content":{"rendered":"\n

Dear Customer,<\/p>\n\n\n\n

Zoho Team is in the process of moving from Dot <\/strong>(.) notation in API Names to the Double Underscore<\/strong> ( _ _ ) notation for all components created in Zoho Extensions.<\/p>\n\n\n\n

Usage of Dot notation<\/strong> will be deprecated by May 20th 2020, <\/p>\n\n\n\n

Zoho Team will migrate all the orgs and extensions by 20th May to compatible versions. All the Orgs having SMS-Magic Interact version 11 or later, will be migrated by Zoho to SMS-Magic Interact version 22.<\/p>\n\n\n\n

SMS Magic has released version 22 on Zoho Marketplace<\/a>, You can update it by yourself manually from Marketplace<\/a> to version 22.<\/p>\n\n\n\n

How it will impact SMS Magic Customers<\/strong> -:<\/p>\n\n\n\n

All the API Name references will be updated to the new notation throughout our extension (Custom Function, Widget Code, External API’s ),<\/p>\n\n\n\n

If you do not have <\/strong>any custom function\/Widget Code or External API\u2019s implemented, then you just need to upgrade the extension.<\/p>\n\n\n\n

In ZOHO CRM, go to Setup > Developer Space > APIs. If the API dashboard displays a banner that your application uses the v1.0 APIs and you have any custom function\/Widget Code or External API\u2019s implemented, you need to make sure that old notations are replaced with new notations as mentioned in below example-:<\/p>\n\n\n\n

Old Notation: smsmagic4.ExternalId , smsmagic4.SMS_History\nNew Notation: smsmagic4__ExternalId , smsmagic4__SMS_History<\/em><\/strong><\/pre>\n\n\n\n
For more information, please refer to https:\/\/help.zoho.com\/portal\/en\/community\/topic\/migration-of-zoho-crm-apis-and-functions-to-v2-0<\/a> .<\/p>\n\n\n\n
Attaching sample code snippets to highlight the changes required in custom functions and widgets below.<\/p>\n\n\n\n
Custom Functions :\u00a0<\/strong><\/p>\n\n\n\n
Old Notation:<\/strong>\nnewRecordInfo = Map();\nnewRecordInfo.put(\"Name\",\"Property One\");\nnewRecordInfo.put(\"sample.Apartment_Name<\/strong>\",property.get(\"sample.Apartment_Name<\/strong>\"));\nresponse = zoho.crm.create(\"sample.Properties<\/strong>\",newRecordInfo);\ninfo response;<\/pre>\n\n\n\n
New Notation:<\/strong>\nnewRecordInfo = Map();\nnewRecordInfo.put(\"Name\",\"Property One\");\nnewRecordInfo.put(\"sample__Apartment_Name<\/strong>\", property.get(\"sample__Apartment_Name<\/strong>\"));\nresponse = zoho.crm.create(\"sample__Properties<\/strong>\", newRecordInfo);\ninfo response;<\/pre>\n\n\n\n
Widgets :\u00a0<\/strong><\/p>\n\n\n\n
Old Notation:<\/strong>\nZOHO.CRM.CONFIG.getOrgVariable(\"sample.oauthtoken<\/strong>\")\n.then(function(data){\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0console.log(data);\n});\nvar recordData = {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"sample.Apartment_Name<\/strong>\": \"Skyline\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"Name\": \"Property One\"\n}\nZOHO.CRM.API.insertRecord({Entity:\"sample.Properties<\/strong>\", APIData:recordData})\n.then(function(data){\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0console.log(data);\n});<\/pre>\n\n\n\n
New Notation:<\/strong>\nZOHO.CRM.CONFIG.getOrgVariable(\"sample__oauthtoken<\/strong>\")\n.then(function(data){\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0console.log(data);\n});\nvar recordData = {\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"sample__Apartment_Name<\/strong>\": \"Skyline\",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\"Name\": \"Property One\"\n}\nZOHO.CRM.API.insertRecord({Entity:\"sample__Properties<\/strong>\",APIData:recordData}).then(function(data){\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0console.log(data);\n});<\/pre>\n\n\n\n
How to upgrade to New Extension Version<\/strong> -: <\/p>\n\n\n\n
Extension will be automatically updated by Zoho team on 20th May or You can update it by yourself manually from Marketplace<\/a> to version 22.0.<\/p>\n\n\n\n
  1. Got to ZOHO Marketplace, Open SMS-Magic Extension Listing.<\/li><\/ol>\n\n\n\n
    \"\"<\/figure><\/div>\n\n\n\n
    1. Click on Install to start the upgrade process -: <\/li><\/ol>\n\n\n\n
      \"\"<\/figure><\/div>\n\n\n\n
      1. Once you click on Install, it will give you details about the upgrade (current version of SMS Magic Extension along with a new extension it is going to update to).<\/li><\/ol>\n\n\n\n
        \"\"<\/figure><\/div>\n\n\n\n
        1. You need to select \u201cI have agreed to the Terms of Service\u201d and \u201cI authorize SMS Magic Interact to access and process my data required.\u201d checkboxes so that you continue with the upgrade.<\/li><\/ol>\n\n\n\n
          1. Choose Users\/ Profiles to which it should be accessible and confirm <\/li><\/ol>\n\n\n\n
            \"\"<\/figure><\/div>\n\n\n\n
            1. After Successful upgrade, the below screen will appear. It means the upgrade process of SMS magic Extension which is compatible with new API 2.0 of ZOHO is done. <\/li><\/ol>\n\n\n\n
              \"\"<\/figure><\/div>\n\n\n\n
              You should be able to use SMS Magic Package hassle free. For assistance or queries, please contact care@screen-magic.com<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
              Dear Customer, Zoho Team is in the process of moving from Dot (.) notation in API Names to the Double Underscore ( _ _ ) notation for all components created in Zoho Extensions. Usage of Dot notation will be deprecated by May 20th 2020,  Zoho Team will migrate all the orgs and extensions by 20th […]<\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"lsvr_kba_cat":[24],"lsvr_kba_tag":[],"class_list":["post-770","lsvr_kba","type-lsvr_kba","status-publish","format-standard","hentry","lsvr_kba_cat-important-announcements"],"_links":{"self":[{"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/lsvr_kba\/770","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/lsvr_kba"}],"about":[{"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/types\/lsvr_kba"}],"author":[{"embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/comments?post=770"}],"version-history":[{"count":10,"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/lsvr_kba\/770\/revisions"}],"predecessor-version":[{"id":789,"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/lsvr_kba\/770\/revisions\/789"}],"wp:attachment":[{"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/media?parent=770"}],"wp:term":[{"taxonomy":"lsvr_kba_cat","embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/lsvr_kba_cat?post=770"},{"taxonomy":"lsvr_kba_tag","embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/converse-release-notes\/wp-json\/wp\/v2\/lsvr_kba_tag?post=770"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}