Paul Hernández (4/4/2013)
Hi Phil thanks for your answer.Now I'm trying to persuade my colleagues to go directly to the database and not over the web service. They allege that write directly is unsupported and I say that the web service for this task is like to go deep in the jungle. The major problem is any modification in any CRM attribute triggers an activity (modification, modified by, modified on). Some fields have additional events.
Even worst, I cannot dynamically configure the mappings in the component that calls the web service.
I will try to convince them to use dynamic SQL queries intead.
Kind Regards,
I suspect that they are correct in their allegations of no support for direct access. But that sure makes things difficult for you - those 'triggers' are presumably set off by the web service call and that's a black box - you don't know what they're doing, other than by observation.
I'll sign off at this point because I don't think I can help. I would not expect the web service method to ever be quick for bulk update operations, so matter how much you refine things - maybe you should cross to the dark side and frequent a CRM forum to see whether they have any suggestions.
Actually, I did have one idea. Writes to the database may be unsupported, but what about reads? These reads could, perhaps, be used to (relatively) quickly identify which columns need to be updated, with just the updates being pumped through the treacle-like update web service.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.