Hey, everybody, Larry’s opportunity pipeline this month is again bigger than everyone else’s. Larry, what’s your secret? Larry, being somewhat softened by reasonable quantities of flavored C2H5OH, was more than happy to share his fortunes: It’s all about power of automatic workflows, my friends. See how I automatically increase opportunity value the moment it’s created? […]
The goal functionality in Microsoft Dynamics CRM is very powerful, but in my opinion, is not used as often as it should be. One of the reasons for this is because goals do not recreate themselves–you must recreate them for each time period. This can be very cumbersome, especially if the time periods are short. […]
Ever wish you could use a workflow to update related/child records? For example, when I update the address on an account, update the address on all of the related contacts. You can, with the help of the very helpful CRM 2011 Distribute Workflow Activity assembly written by Alberto Gemin on Codeplex. While this says “CRM 2011” […]
So you create a real-time (synchronous) workflow, and when you test it out, it doesn’t do anything. Say you have a workflow that should fire when an opportunity status is changed to “Won,” but you close an opportunity as “won,” and nothing happens, and there are no errors. Most likely, you have the workflow definition […]
This week has all been about workflows and waiting. To finish it off, we’d like to present a short video demonstrating how to schedule a long running process (sending anniversary gifts to contacts in this case) without creating a bunch of forever waiting workflows. It’s done by using wonderful solution by Lucas Alexander. We also […]
Despite of what we said earlier this week, wait can be a very powerful instrument. My fellow tipster Joel suggested in his last tip some fine tuning when it comes to wait: Combine waits and check condition. So you have a process that emails a customer service representative three days after the case is open. […]
This week’s tips all seem to be about workflows and here is an old favorite of mine. I always found it interesting how non-intuitive wording around Timeout condition pushed majority of developers to use rather convoluted but easier to read and understand Wait conditions when a workflow needs to be paused for a fixed duration. […]
In yesterday’s tip we suggested to avoid wait conditions altogether; but if you must use them: Combine waits and check condition. So you have a process that emails a customer service representative three days after the case is open. No need to email them if the case has been closed, right? After the wait, have […]
Workflow wait conditions can be very useful. Say you need to have an email go to a customer 30 days prior to their contract renewal, it can be tempting to use a wait condition. However, excessive use of wait conditions has a downside. Performance: each waiting workflow instance carries performance overhead. The more waiting workflow […]
If you decided to follow our previous tip and cancel workflows only when necessary, you may wonder what does the Set Properties button for this step do. As it turns out, stopping workflow has a single property called Status message: The best use of this property comes with the new real-time workflows in CRM 2013. […]
of the