Writing to a multiselect user field

Hi,

Just wondering if anyone can provide advice about how to write to a multiselect user lookup field.

I've tried a number of approaches but none work.

I'm fairly new to Deluge, so would be grateful for any advice. This is a long post, so I really appreciate anyone who takes the time to scan through what I've done and provide suggestions on how to make something work.

------------------------------

Here's method #1:

SubDetails = zoho.crm.getRecordById("Subscriptions",SubId.toLong());

newlist = List();

oldlist = ifnull(SubDetails.get("Observers"),"").toList();

newlist.add(oldlist);

newlist.add({"name":"John XXX","id":"2396546000013610003"});

info newlist;

updateResp = zoho.crm.updateRecord("Subscriptions",SubId.toLong(),{"Observers":{"name":"John XXX","id":"2396546000013610003"}});

info updateResp;

where Subscriptions is a custom module and Observers is a multiselect user lookup field.

The response I get is:

newlist is

[],{"name":"John XXX","id":"2396546000013610003"}

And updateResp indicates success, but no change is made to the record :(

The other problem is that newlist should include the Observers already added to that Subscription, but it does not.

------------------------------

A bit more googling and I was onto method #2:

mp = Map();

mp.put("field0",{"name":"AFS Test Subscription","id":"2396546000024420120"});

mp.put("Observers",{"name":"John XXX","id":"2396546000013610003"});

createResp = zoho.crm.createRecord("Subscriptions X Users",mp);

info mp;

info createResp;

where Subscriptions X Users is the API name for the linking module, and field0 is the API name for the field within that linking module for the Subscription lookup.

The response is:

mp is:

{"field0":{"name":"AFS Test Subscription","id":"2396546000024420120"},"Observers":{"name":"John XXX","id":"2396546000013610003"}}

but unfortunately createResp is

{"status":"failure"}

------------------------------

After reading more docs, I was onto method #3:

createResp = zoho.crm.bulkCreate("Subscriptions X Users",{{"field0":{"name":"AFS Test Subscription","id":"2396546000024420120"},"Observers":{"name":"John XXX","id":"2396546000013610003"}}});

info createResp;

For this method, the response is:

createResp is:

null

------------------------------

If you've made it this far into my post thank you! I hope this leads to a solution that will hopefully help others in future too.

Access your files securely from anywhere

Zoho Developer Community

New to Zoho LandingPage?

Access Zoho LandingPage

Zoho LandingPage Resources

New to Zoho Survey?

Access Zoho Survey

Latest Feature Updates

Explore our Pricing & Plans

Zoho Survey Resources

Android Mobile Surveys

Insurvey Blogs

Insight Blogs

Tips & Tricks

New to Zoho CRM Plus?

Deliver unforgettable customer experiences

ACCESS ZOHO CRM PLUS

New to Zoho CRM Plus?

Deliver unforgettable customer experiences

ACCESS ZOHO CRM PLUS

New to Zoho Marketing Plus?

Everything you need to run your marketing

ACCESS ZOHO MARKETING PLUS

New to Zoho Marketing Plus?

Everything you need to run your marketing

ACCESS ZOHO MARKETING PLUS

New to Bigin?

Signup Now

Access Bigin

Latest Feature Updates

Zoho Desk Resources

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

Tout forum

France ZUGs

Zoho SalesIQ Resources

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