![]() ![]() Moves the selected message to a mail folder that you specify and marks the message as read.įorwards the message to your manager. For example, if you want a Quick Step to move messages to a certain folder, you must specify the folder before you can use the Quick Step.ĭefault Quick Steps in Outlook include the following: When you use some Quick Steps for the first time, you are prompted to configure them. You can customize any of the default Quick Steps. This is because Quick Steps can contain actions such as Permanently Delete that are not able to be undone. There are so many people using this software, you can't be the only one who has ran into this issue.Note: Quick Steps cannot be undone using a menu command or with a keyboard shortcut like Ctrl+Z. The biggest tip I can give you is, when there is an issue, don't panic! Most Microsoft CRM issues can be resolved by following these basic methods of debugging. I cannot stress how important it is to have a good partner in times of need! I know this may sounds like an obvious answer, but when all else fails, make sure you have a good partner. If you are really stuck, I have found Microsoft to be very helpful if you can tell them what your exact problem is. One of the reason why I love working with Microsoft CRM is because of the "openness and coolness" of the community :). ![]() And I think Google is only really useful because the Microsoft CRM community is so open about knowledge sharing. But honestly, I found Google to be the most useful resources when it comes to resolutions. Hopefully, you can come up with a strategy to resolve the issue once you find it. As our magical DBA puts it, everything goes back to the database. If the issue seems to be data related and some what mysterious, it is always a good idea to check the Database connections and transactions. This is a trick I learned recently, and hopefully you have a good DBA around you to help with this one. Here is a cool little tool you can use to enable tracing in CRM 2011. Though I have found it to be painful to read the trace logs. #Debugging microsoft outlook quick steps how toHere is a handy article on how to get the event viewer if you didn't know already -įor everything else, you can always enable trace. You would be surprised at how simple and effective this method is. Simply go there to see if there is an error related to CRM and just google to Event ID. ![]() If it is not customization related, I have found the event viewer on the server to be my best buddy. ![]() There are several ways to identify the issue once you have pinned down the source of the issue. Here is a list of places that the issues can happen from - form, script, workflows, plug-ins, data, database, server and most often, users. Finding the source of the issue is key in debugging Microsoft CRM problems. Most of time, finding the issue is almost 90% of the battle. Here is quick overview of my debugging methods -Īs the saying goes, recognizing the problem is the first step to resolving it. Mainly because we were partner-less for quite some time and Microsoft always took a mysteriously long time to even figure out what was wrong. Then I got a chance to lead the Microsoft CRM Scooby Doo team at my current job where our responsibility was to solve all issues related to CRM on our own. And if all else failed, we had Microsoft to call, though, it is always a hit or miss with those lovely folks. I didn't have to do a lot of technical debugging because there were developers and infrastructure consultants for all those "pesky" issues. I started out as a functional consultant in my Microsoft CRM career. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |