Results 1 to 8 of 8

Thread: The record could not be updated due to a permissions issue

  1. #1
    RADIX is offline Member
    Join Date
    Jul 2010
    Posts
    12

    Default The record could not be updated due to a permissions issue

    Hello

    After I import the contacts by specifying the option "Create and Update Records", I get an error file named "error_1.csv" which contains an error message for each contact :

    "The record could not be updated due to a permissions issue"

    Also, there are some contacts that are added as well (instead of being updated) when they already existed.

    Is there a solution for the update goes properly?

    Thank you.
    Last edited by RADIX; 2010-09-02 at 01:42 PM. Reason: Instant notification

  2. #2
    ben.gillis is offline Senior Member
    Join Date
    May 2010
    Location
    Pittsburgh PA
    Posts
    61

    Default Re: The record could not be updated due to a permissions issue

    very interesting. i would try and check permissions for this module. you want to make sure that 1 you have permissions to create records in the module, and 2 that if using field lever permissions you are not trying to update a field that is read only. to do this check permisisons to the module for your role.

    hope this helps.

    Ben Gillis
    SugarCRM Trainer
    Plus Consulting
    http://www.plusconsulting.com/training.htm

  3. #3
    RADIX is offline Member
    Join Date
    Jul 2010
    Posts
    12

    Default Re: The record could not be updated due to a permissions issue

    Hi ben,

    Thank you for your reply.

    I am a Sugar administrator and all of my roles and permissions are activated.
    All contacts have their ID in the import file.
    And still, I get the same error.

    Thank you for your help.

  4. #4
    mindkiller is offline Junior Member
    Join Date
    Oct 2010
    Posts
    3

    Default Re: The record could not be updated due to a permissions issue

    Hi,

    I have the same problem, or at least I think I do.

    I can import contacts easily, but then when trying to update accounts details with fields such as website and so on, I get an error with permissions for each ID.

    What's the way around it?

    a) Am I doing this right?
    b) how can I check if I have got all permission set correctly?

    Many thanks

  5. #5
    eitrix's Avatar
    eitrix is offline Sugar Community Member
    Join Date
    Aug 2010
    Location
    Serbia
    Posts
    396

    Default Re: The record could not be updated due to a permissions issue

    check permissions of your db user maybe?
    CRM Software Engineer
    Eontek - www.eontek.rs

  6. #6
    evallgar's Avatar
    evallgar is offline Sugar Community Member
    Join Date
    Jan 2007
    Location
    Monterrey, MX
    Posts
    11

    Default Re: The record could not be updated due to a permissions issue

    I was able to import records into Contacts module using Chrome Browser. I've been trying to do the same from ANY other browser unsuccessfully.

    Weird, isnt it?

    Guys, I think I found a solution. Try not mapping ID field.

    PS Forget about the browser stuff ... sorry.
    Last edited by evallgar; 2011-01-14 at 10:44 PM. Reason: Probably found a solution

  7. #7
    rya
    rya is offline Member
    Join Date
    Feb 2011
    Posts
    8

    Default Re: The record could not be updated due to a permissions issue

    I know this is an old thread, but since someone else brought back from the dead, I'll keep it alive just a little longer..

    I'm having the same permissions issue, and I'm sure it's the ID field. I plan on doing regular exports out of an ERP system into Sugar (accounts), and I thought that using the ID field mapped to the ERP account ID was a great way to keep track of this. The other reason I used ID is that I've got some sub-accounts that are members of the master account, and was able to use that ID in the parent_id field of these sub-accounts. Is there any way to use ID?
    Otherwise, I think I'll have to do the following:
    1. Just let SugarCRM create it's own ID
    2. Create a special 'erp_id' field, then a special 'parent_of_erp_id' field, and associate them just like parent_id is doing it
    3. Make sure it looks at this erp_id field when doing an import so that it updates the account records instead of creating new ones
    4. Add everything to the various forms (I assume that's possible through studio, even though I haven't tried).


    Any ideas on just using ID?

    thanks,

    -Ray

  8. #8
    rya
    rya is offline Member
    Join Date
    Feb 2011
    Posts
    8

    Default Re: The record could not be updated due to a permissions issue

    I figured it out.. You can't import a record whose ID matches one that is set to 'deleted' in the DB.

    I manually set the deleted column in the db to 0 and the import went through just fine.

    It would be nice if the import failure results mentioned that, instead of just a generic 'Permission Denied'.

    thanks,

    -Ray

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Per-record Permissions (Roles)
    By kovshenin in forum Help
    Replies: 3
    Last Post: 2010-05-23, 09:38 PM
  2. Permissions Issue
    By Shoregeek in forum Help
    Replies: 2
    Last Post: 2006-03-03, 11:44 AM
  3. Installation Issue with Permissions
    By KMulligan in forum Help
    Replies: 1
    Last Post: 2005-09-19, 07:32 AM
  4. config.php permissions issue
    By smueller72 in forum Help
    Replies: 0
    Last Post: 2005-07-29, 08:12 PM
  5. Another Permissions issue
    By gavin in forum Help
    Replies: 4
    Last Post: 2005-02-24, 03:20 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •