Create/Update Deal with Pipeline value cannot use Deluge, only RESTAPI

Hi everybody,

it has been a long time since I posted a topic. Today however, warrants a comeback as I personally think that this information would be beneficial for the community. If you are looking to update or create a deal and want to specify a pipeline, please note that you cannot do it using Deluge, as in zoho.crm.updateRecord or zoho.crm.createRecord. You might notice that zoho.crm.getRecordById or getRecords also do not include the Pipeline information in the return values.

The only way to do it; either to get, update, or create with a Pipeline value is to do it using RESTAPI. Since V2.1, this has been supported, I believe. The method is still simple; just pass a value to "Pipeline" key with the actual name of the pipeline. This is the V7 documentation on it, https://www.zoho.com/crm/developer/docs/api/v7/insert-records.html. And please note that this method now allows multiple records creation, so you would to pass the value of "data" as an array, e.g:

fieldValues = Map(); //this is the map data type to host all the fields' values in 1 record
fieldValues.put("Pipeline","your pipeline name");
fieldValues1 = Map(); //this is the map data type to host all the fields' values in another record, different from above
fieldValues1.put("Pipeline","your pipeline name");
recordlist = List(); //this is to hold all the information of the multiple records. you might have fieldValues, fieldValues1, etc
recordlist.add(fieldValues,fieldValues1);
dataValues = Map();
dataValues.put("data",recordlist);
createRecords = invokeUrl
[
url: "https://www.zohoapis.com/crm/v7/Deals"
type: POST
parameters: dataValues.toString() //dont ask me why we have to put toString. In my experience, it doesnt work if we dont do this
connection: "yourConnectionName"
];

This is specifically for creating new deal records.

On that note,

This might be just me, but I do find it a little bit weird not to have this capability in normal Deluge. We all know that Deluge is far easier to write and to understand than RESTAPI. The exclusion of some select information is thus perplexing to say the least. This prevents the users from just doing something in one method and effectively forcing them to learn RESTAPI as well, when they don't need to if Deluge is good enough. This roadblock certainly adds to the level of complexity of learning custom function in Zoho CRM.

I hope the product team sees this and starts to wonder from the users' point of view. What makes sense, and what doesn't.

As always, good luck.

Zoho Desk Resources

Desk Community Learning Series
Digest
Functions
Meetups
Kbase
Resources
Glossary
Desk Marketplace
MVP Corner
Word of the Day

Topic Participants
Nik

Sticky Posts
Zoho CRM Functions 53: Automatically name your Deals during lead conversion.
Welcome back everyone! Last week's function was about automatically updating the recent Event date in the Accounts module. This week, it's going to be about automatically giving a custom Deal name whenever a lead is converted. Business scenario Deals are the most important records in CRM. After successful prospecting, the sales cycle is followed by deal creation, follow-up, and its subsequent closure. Being a critical function of your sales cycle, it's good to follow certain best practices. One such
Custom Function : Automatically send the Quote to the related contact
Scenario: Automatically send the Quote to the related contact. We create Quotes for customers regularly and when we want to send the quote to the customer, we have to send it manually. We can automate this, using Custom Functions. Based on a criteria, you can trigger a workflow rule and the custom function associated to the rule and automatically send the quote to customer through an email. Please note that the quote will be sent as an inline email content and not as a PDF attachment. Please follow
Function #50: Schedule Calls to records
Welcome back everyone! Last week's function was about changing ownership of multiple records concurrently. This week, it's going to be about scheduling calls for records in various modules. Business scenario Calls are an integral part of most sales routines.. Sales, Management, Support, all the branches of the business structure would work in cohesion only through calls. You could say they are akin to engine oil, which is required by the engine to make all of it's components function perfectly. CRM
Function #37: Create a Purchase Order from a Quote
Welcome back everyone! Last week, we learnt how to calculate the total number of activities for a lead and further take note of the activity count for particular dates. For instance, from the period of Demo to Negotiation. This week, let's look at a function that lets you create a Purchase Order instantly from a Quote. Business scenario: In any form of business, one of the most important things to do is to document the transactions. Naturally, negotiation, signing an agreement, placing an order,
Function-2: Round-Robin assignment of records
Welcome back folks! Last week, we saw how to update sales commission in quotes using a custom function. This week, let's see an interesting use case asked by many of you - auto-assignment records by round-robin method. Business scenario: Right now, the solution allows you to auto-assign leads from web form and imported lists. Let us look at a need where you want to auto-assign leads from in-bound calls in a round-robin method, across modules. Prerequisite: You must create a permanent record in the