Importing Opportunities and Permissions

[jleaman]

When creating/updating records on a Opportunities import I get the following error:

"The record could not be updated due to a permissions issue" I find this error in the error_1.csv file.

I have reviewed the permission settings for the file system and made sure to follow suit with no luck. Any ideas?

[salesagility]

Do all the records get rejected or just one record?

[jleaman]

As far as I can tell, all. I am importing a portion of my list (300 entries). Watching the error file will show me that this error is printed about 6-15 times before the import fails and reports 0 entries imported. Sugar doesn't report this error to me in the webgui..

I also checked the permissions of the defined user in the DB. This showed that the user had all privileges.. so that's out of the question.

[jleaman]

I did find this line in the en_us.lang.php file:

'LBL_RECORD_CANNOT_BE_UPDATED' => 'The Record could not be updated due to a permissions issue',

Where is this defined so I can see where this error is originating from? This is very strange.

[rrichey4430]

In my case, this problem resulted because I originally had two duplicate records with the same information in them, but of course, each had its own unique ID. I had previously "deleted" one of the two duplicates. When I was doing the import, I was inadvertently using the ID of the "deleted" record instead of the ID of the ongoing record.

When you delete a record in sugar, the record is actually not really deleted, but is simply flagged as having been deleted. In most circumstances, sugar behaves as if the record were in reality "gone". But when importing by ID with the express purpose of updating records, referencing the ID of one of these "deleted" records caused this "permissions" error message to be displayed, since the "deleted" record is effectively (and correctly) locked to any and all updates.

So, to solve my problem, I simply replaced the erroneous "deleted" ID with the correct, ongoing ID for the duplicated record in my import file.

If any of the Sugar gods ever read this note, it would sure be nice if you could make such messages a bit more explicit. In this case, something like, "The ID is locked because it corresponds to a record that has been previously deleted" would be really nice...