Resources for IT Professionals >
Dynamics Forums
>
CRM
>
reassign records not working from user window
reassign records not working from user window
- Hi,
I am trying to Reassign the records from one user to another user. I have navigated to that user window and from there from actions i have clicked on "Reassign Records". After some time i am getting the poop up saying "An error has occured."
What could be the reason for this? Can any pls suggest.
Thanks
Answers
- This could be security related. I am not sure what records you are trying to re-assign, but check to ensure the user who will become the owner of the records has rights to own those and the related child records. For example, if you are re-assigning Accounts, that might mean that related Contacts, Activities, Quotes, Opportunities, etc., will move to the new owner depending on how you have your system configured. Check the cascading behavior of the entity records and the security settings for the new owner to ensure the owner is not restricted in some way.
You can also turn Dev errors on to see if you receive a more descriptive message.
Best Regards, Donna- Proposed As Answer byDonna EdwardsMVP, ModeratorTuesday, August 25, 2009 7:50 PM
- Marked As Answer byDonna EdwardsMVP, ModeratorThursday, August 27, 2009 9:01 PM
- could be a couple of things.
There is an issue where you cannot reassign some records, like accounts if the database has queueitem records that have null organizationid's. This has been known to happen with some upgrades from 3.0.
If you reinstall crm on your server and choose to download the latest installation files, this will fix that issue, if you have it
Another way to fix this issue is to run the following query against your MSCRM database in SQL. Back up before you do it.
UPDATE QueueItemBase
SET OrganizationId = (SELECT Organizationid FROM OrganizationBase) WHERE OrganizationId IS NULL
If that doesn't fix your issue, I would recommend that you download the crm 4 diagnostic tool from http://blogs.msdn.com/benlec/archive/2008/03/04/crmdiagtool4-for-microsoft-crm-4-0-has-been-released.aspx
run it on the server, turn on dev errors, turn on tracing, recreate the issue, turn off traces, zip trace files, open the log file from the zip and you should be able to find more detailed error information.- Proposed As Answer byDonna EdwardsMVP, ModeratorTuesday, August 25, 2009 7:50 PM
- Marked As Answer byDonna EdwardsMVP, ModeratorThursday, August 27, 2009 9:00 PM
All Replies
- This could be security related. I am not sure what records you are trying to re-assign, but check to ensure the user who will become the owner of the records has rights to own those and the related child records. For example, if you are re-assigning Accounts, that might mean that related Contacts, Activities, Quotes, Opportunities, etc., will move to the new owner depending on how you have your system configured. Check the cascading behavior of the entity records and the security settings for the new owner to ensure the owner is not restricted in some way.
You can also turn Dev errors on to see if you receive a more descriptive message.
Best Regards, Donna- Proposed As Answer byDonna EdwardsMVP, ModeratorTuesday, August 25, 2009 7:50 PM
- Marked As Answer byDonna EdwardsMVP, ModeratorThursday, August 27, 2009 9:01 PM
- could be a couple of things.
There is an issue where you cannot reassign some records, like accounts if the database has queueitem records that have null organizationid's. This has been known to happen with some upgrades from 3.0.
If you reinstall crm on your server and choose to download the latest installation files, this will fix that issue, if you have it
Another way to fix this issue is to run the following query against your MSCRM database in SQL. Back up before you do it.
UPDATE QueueItemBase
SET OrganizationId = (SELECT Organizationid FROM OrganizationBase) WHERE OrganizationId IS NULL
If that doesn't fix your issue, I would recommend that you download the crm 4 diagnostic tool from http://blogs.msdn.com/benlec/archive/2008/03/04/crmdiagtool4-for-microsoft-crm-4-0-has-been-released.aspx
run it on the server, turn on dev errors, turn on tracing, recreate the issue, turn off traces, zip trace files, open the log file from the zip and you should be able to find more detailed error information.- Proposed As Answer byDonna EdwardsMVP, ModeratorTuesday, August 25, 2009 7:50 PM
- Marked As Answer byDonna EdwardsMVP, ModeratorThursday, August 27, 2009 9:00 PM
- I've seen this when one of the records is deactivated/disabled.Leon Tribe
Want to hear me talk about all things CRM? Check out my blog
http://leontribe.blogspot.com/or hear me tweet @leontribe
Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe - Were you able to resolve the issue with any of these suggestions or did you find a different solution? Please provide an update in the event your resolution helps someone else. Thank you
Best Regards, Donna Can you paste View State, error?
- I didnt get time to work on this. Will update you soon with my implemenation.
- I had a similar problem and discovered that I was missing records in the CustomerAddress entity. I suspect this was due to some problems we had using the data migration tool or data import in CRM.
Each Account record requires 2 CustomerAddress records, and if those records are missing, then assigning the account to another person wont work. if you turn on CRM trace (http://support.microsoft.com/default.aspx/kb/907490), you are likely to see an error message like:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidCastException: Specified cast is not valid.
at Microsoft.Crm.BusinessEntities.AddressTrigger.Update(Guid id) ...
Try running this query and if you get any results, then you are missing records from CustomerAddress:
select * from account where accountid not in (select parentid from customeraddress)
My solution was to use the SQL Profiler tool to see what CRM was inserting into that table when a new account was created, and I wrote a couple SQL lines that would insert (effectively) blank records in the CustomerAddress entity only for the accounts that had missing address records:
insert into CustomerAddressBase
(PARENTID, CUSTOMERADDRESSID, ADDRESSNUMBER, OBJECTTYPECODE, CREATEDBY, CREATEDON, MODIFIEDBY, MODIFIEDON, DELETIONSTATECODE)
select accountid, newid(), 1, 1, (SELECT systemUserID FROM SystemUserBase WHERE firstname='First name ' ), getdate(),(SELECT systemUserID FROM SystemUserBase WHERE firstname='First name ' ), getdate(),0
from accountbase where accountid not in (select parentid from CustomerAddressBase where ADDRESSNUMBER=1)
insert into CustomerAddressBase
(PARENTID, CUSTOMERADDRESSID, ADDRESSNUMBER, OBJECTTYPECODE, ADDRESSTYPECODE, FREIGHTTERMSCODE, SHIPPINGMETHODCODE, CREATEDBY, CREATEDON, MODIFIEDBY, MODIFIEDON, DELETIONSTATECODE)
select accountid, newid(), 2, 1, 1, 1, 1, (SELECT systemUserID FROM SystemUserBase WHERE firstname='First name ' ), getdate(),(SELECT systemUserID FROM SystemUserBase WHERE firstname='First name ' ), getdate(),0
from accountbase where accountid not in (select parentid from CustomerAddressBase where ADDRESSNUMBER=2)
Just an aside: I have heard that MS technical support will not be happy if you admit to them that you have been inserting records manually, but I dont see any other options other than deleting all those accounts (and activities, etc) through the UI and try to re-import them.
HTH
Nelson Johnson- Proposed As Answer byeccountable Saturday, November 07, 2009 5:58 AM
