Populating a user pick list failing if user is not an admin or portal owner

I have a function that, until recently worked fine. The function essentially copies another project. One aspect of this copying was to take the value of a UDF that is a User Pick List, find the correct user id for that user, and populate the corresponding pick list UDF in the target project.

Recently (I can't say exactly how long ago), this aspect of the copying started to fail, and actually caused the entire copying to fail. I've isolated the user pick list updates and removed them from the main update, so MOST of my copy process works.

The curious thing about this is, if the ID on the "source" project belongs to a user who is an Admin or the Portal Owner, the population of the "Target" project's User Pick List field works just fine. Any other user profile seems to cause it to fail.

The gist of how I do this is to get a list of portal users, and compare the user to my "source" user:

userresp = invokeurl

[

url :endPoint + portalId + "/users/"

type :GET

connection:"projectusers"

];

//info userresp;

users = userresp.getJSON("users").toJSONList();

for each user in users

{

curruser = user.getJSON("name");

if(curruser == salesperson1)

{

salesperson1id = user.getJSON("id");

//info "Sales Person: " + salesperson1;

//info "Sales Person ID: " + salesperson1id;

}

...

}

I then try an update using a map with this entry:

editmp2.put("UDF_USER1",salesperson1id);

if salesperson1id belongs to an admin or portal owner, everything works. The other profiles fail.

Any help?

Thanks,

George

Zoho Desk Resources

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

Topic Participants
George Fehrenbach
Monica P

Sticky Posts
Building extensions #10: Fetch customized user inputs, store them globally at the app level, and access them across entities
This data storage concept enables you to store data related to your extension for both entity properties and extension properties. In our previous piece, we looked at how to store data for entities using entity properties. In this post, we'll look at
Building extensions #9: Store, retrieve, and access entity-specific data in widgets using data storage
Data storage - Overview Storing data related to the extension you are working on is essential. It can be saved as key-value pairs for an entity or extension, known as entity and extension properties, respectively. Data can be saved for the following entities
Building extensions #7: Create custom widgets for a simplified end-user experience
Discover the benefits of using widgets! We explored the significance of widgets, prerequisites, and the availability of JS SDK methods as part of our previous post. In this post, let's go over a detailed example of using widgets along with certain Zoho
Building extensions #6: Custom user interfaces with Widgets
Welcome to our post on Widgets for Zoho Projects! In our last post, we explored the significance of the connections feature, showed how to use it, and provided an example use case. In this article, we'll look at the importance of widgets, another feature
Building extensions #5: Integrating applications with Zoho Projects through Connections
In our last post, we discussed the essential features that a Zoho Projects extension can provide. Starting with this post andin every subsequent post going forward, we'll go through each of those features in depth, one by one, with an example use case.