I have found a “workaround” by unchecking the “Prevent private data” checkbox in the User Accounts section.

But the contact that is created through the API shouldn’t be private.

Does anybody know how to handle this? So that in the end the contact created through the API is not private.

dennisdegrauw - Mar 11, 2010 04:55am

I have found a “workaround” by unchecking the “Prevent private data” checkbox in the User Accounts section.

But the contact that is created through the API shouldn’t be private.

Does anybody know how to handle this? So that in the end the contact created through the API is not private.

You should provide ‘ownership’ to set some specific group as the owner of the contact. If you don’t send it - contact is being created private (and fails if private is not allowed).

Alex - Mar 11, 2010 06:06am

dennisdegrauw - Mar 11, 2010 04:55am

I have found a “workaround” by unchecking the “Prevent private data” checkbox in the User Accounts section.

But the contact that is created through the API shouldn’t be private.

Does anybody know how to handle this? So that in the end the contact created through the API is not private.

You should provide ‘ownership’ to set some specific group as the owner of the contact. If you don’t send it - contact is being created private (and fails if private is not allowed).

Thanks Alex, this did the job!

You are always welcome.

Still having this error.
We have set the ownership for the user we are using to talk to the API
as the owner of all contacts.
Any idea why this might be happening.

POST https: //secure.solve360.com/contacts HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Accept: application/xml
Authorization: Basic ********************
Host: secure.solve360.com
Content-Length: 14

firstname=ADAM

Error:
401
permissionsitemadd
|-You do not have sufficient permissions to create items of specified type

Maybe you can give me some instructions on the “ownership” part, as I have to forwarded it to a non-technical person.

Hey Aman,

Sure private data is not disabled for the user? Can be checked under “Modify User Accounts”: “prevent private data” should not be checked.

Regards,
Alex.

Alex - Jan 07, 2012 10:02pm

Hey Aman,

Sure private data is not disabled for the user? Can be checked under “Modify User Accounts”: “prevent private data” should not be checked.

Regards,
Alex.

Thanks Alex.
The confusion was that I wasn’t passing the “ownership” code to the API. I thought this was a setting that had to be done for a group of people in the UI. My bad.
Thanks again.

Maybe a good idea to put that in the API example syntaxes :)
Also is there anyway I can post an example C# application for Norada to be able to share with other developers—making life easy