Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How to do mass update

0 views
Skip to first unread message

odeddror

unread,
Nov 6, 2009, 10:03:56 AM11/6/09
to
Hi there,

We are using CRM 4.0 and
We would like to update the Regional Manager in Account
Based on states (we have aprox 27,000 accounts)
How do I do that (write update query against Account table)?

Thanks,
Oded Dror

Joe Gill

unread,
Nov 9, 2009, 11:49:56 AM11/9/09
to

Hi Oded,

Updating the CRM tables directly is not supported and you should use
the web service to do an update.

Sorry
Joe

rakesh

unread,
Nov 10, 2009, 7:27:04 AM11/10/09
to

hi Oded

You can do it using advance find

search for the records action update record

regards
rakesh Agarwal
r...@mtccrm.com
www.dynamicsexchange,com

Dave

unread,
Nov 10, 2009, 10:59:14 AM11/10/09
to

Oded,
There are two other supported ways to do the bulk edit, if you don't
have .Net coding resources at your disposal:
1) Bulk Edit
2) Workflow

With 27,000 accounts, Bulk Edit would be pretty tedious, as you can
only edit 250 records at a time... But that is the lowest cost low
tech way to get the job done. (On the Account grid, select all
records (check the box above the grid) and under Actions, select
Edit. (Now, you can do this with an advanced find too, so you could
find all accounts in WA, e.g., and assign them to the appropriate
manager.)

The workflow is definitely the way I'd go. Not only can it help you
with your current bulk update, but it can be written so that each new
account that gets created could run this workflow rule to update the
Regional Manager based on state. In the workflow, you'd want one IF
statement for each Account Manager.

IF State IN 'WA', 'OR', 'ID',
then Update Account set Regional Manager = 'PacNWSalesRep'

Then, set the workflow to run:
(a) On Demand, so you can run it again the 27,000 accounts
(b) On Create, for when new accounts are created, and
(c) On Update, when the State is changed.

Now, you'll still have to invoke this workflow for the 250 records at
a time, but you don't need to perform queries to limit the records by
state, as your workflow should account for every state...

Now, having said this, if you have a .Net coding resource, and expect
this to be just a one-time update, then using the API to do it would
definiitely be faster. I just wanted to present what might be a more
complete longer term solution, without writing code. HTH,
Dave

-------------------------------------------
David L. Carr, President
Visionary Software Consulting, Inc.
Cell: 503-351-4207
Email: davidlcarr...@earthlink.net
http://www.vscrm.com

0 new messages