Microsoft Dynamics CRM 2011: Updating a lookup field using SQL

0
votes

I have thousands of incidents in my CRM that are either resolved or cancelled. We have added a new lookup field to incident's form recently but of course incidents that are already closed do not have any value in it. It is essential to populate that lookup field for all incidents.

I tried to create a console application that would have updated all closed incidents but apparently I can't update an incident unless I activate it first.

Reopening (and then closing again) any incident at this point is pretty much not wanted solution.

So I was wondering updating that lookup field by writing simple SQL statement. I know this is highly unsupported so my question is what could possible go wrong? I tried to update one incident by using SQL and it seems to work but before I update all of them I want to know why I should no do this? Is it enough to update that one lookup field in a database table (to put relevant GUID into it) or is there something else I should update too?

Or if you have any other solutions how I could populate that field without reopening an incident I'd be happy to hear it.

1
dynamics-crm-2011dynamics-crm
Although unsupported, it is pretty much the only option available in your circumstances. Updates you can get away with, adding or deleting I would never do as it requires extra coordination with tables likes PrincipleObjectAccess – Ben Williams

1 Answers

0
votes

As you already found by SDK you need to reactivate the incident first.

By SQL is unsupported and is preferable to avoid direct updates.

You can face some issues with the SQL way, for example workflows will not be triggered by SQL updates, in your case probably you will not face issues updating closed incidents (probably you need this lookup filled for reporting requirements).

As far as I know if you want to go with SQL you need to update only the single attribute.

Up to you the final decision.