Most organizations implementing Dynamics CRM use the sales functionality. And when you use Dynamics CRM for sales, you generally start with theOpportunity record type. Opportunities represent potential sales, and they can be customized to line up with most organizations’ sales processes. But they had a significant limitation in Dynamics CRM 4.0 that prevented many organizations from taking advantage of some potentially great functionality: unlike the other record types in the Dynamics CRM sales process tetrarchy (quotes, orders and invoices), CRM 4.0 opportunities did not support write-in products.
Yes, I’m aware that a lead-in like that will be considered hard-hitting in only certain circles, and that even if you’re a current happy user of Dynamics CRM opportunities it might not sound like that big a deal. I think it’s important, though, since this one little change – adding support for write-in products to opportunities – allows you to realize several significant benefits for free.
On the default opportunity form in Dynamics CRM 4.0, there’s a field that allows you to select between System Calculated and User Provided pricing. Selecting the User Provided option means you can enter anything you like in the Est. Revenue field. This is easy, but it’s not very scientific! The alternative option — System Calculated pricing — does what it sounds like it would: rather than simply entering a number for estimated revenue, you select products from the product catalog, enter a quantity, and let the system calculate what the revenue will be.
Some of the advantages of system calculated pricing are obvious:
Others aren’t as obvious, especially if you’ve never used it because it was too much of a hassle (I’ll get to that part next). For example, here are two of the most important non-obvious benefits:
But that last bit – about selecting price lists – gets to the reason system calculated pricing was under-used in CRM 4.0, and how the addition of write-in product support in CRM 2011 can help.
The basic problem in CRM 4.0 was that in order to use system calculated pricing, you had to have a completely built-out product catalog. Here was the process:
I’ll spare you the rest of the details, but if you’re getting the idea it was a lot of work, you’ve got the idea. What does any of this have to do with write-in products? Well, it turns out that Write-In Products are the alternative, when adding a line item to a sales transaction, to Existing Products. So, in CRM 4.0, the fact that opportunity records did not support write-in products meant that you had three basic options:
With that background, let’s take a look now at what you can do in Dynamics CRM 2011.
First, the only requirement to use system calculated pricing is that you have a price list you can apply to an opportunity. It does NOT have to have any price list items, which means you can start realizing benefits from system calculated pricing without being required to perform the tedious product catalog configuration tasks first. In the following demonstrations I’ll use an un-customized CRM 2011 organization, but this should work pretty much the same in any organization you’re working in.
If you don’t have one, you can create a price list by following these steps:
Read the rest of the article in Richard Knudson's Dynamics CRM Trick Bag.
Arbor Networks surveyed the single largest attack bandwidth in 2010 at 100 Gbps. This is the first time the attack bandwidth broke that barrier, and it represents a 102% increase over the largest attack in 2009, according to the report. It also represents a 1,000% increase in attack size from when Arbor Networks began its survey in 2005, according to Carlos Morales, vice president for global sales engineering and operations at Chemlsford, Mass.-based Arbor Networks.
Cybercriminals can generate a large volume of traffic due to the proliferation of technology, Morales said. Between smartphones with 3G or 4G capabilities and wired broadband networks, the equipment available for botnet exploitation ranges in the billions of devices and represents far more than the amount of bandwidth available to most network operators, Morales said. Application-layer DDoS attacks, similar to the attacks used in the WikiLeaks debacle by members of the "Anonymous" group, are also becoming more prevalent. These are more difficult to detect and utilize sophisticated tools to generate traffic that firmware handles in some way.
Arbor Networks is tracking an increase in application-layer attacks against critical infrastructure. HTTP and DNS servers are the primary victims; however, these attacks also target SMTP and VOIP infrastructure and are much more serious, Morales said. "The challenge with [application-layer attacks] is these attacks are harder to detect; they're more stealthy, they don't generate a large network bandwidth but they're equally capable of taking down a network," Morales said. The "threat to defense gap" is also as wide as it has been since the inception on DDoS, Morales said. This is largely due to the current practice of defenders using traditional means, such as firewalls, to defend their servers and datacenters. Firewalls specifically protect against infiltration attacks and block unsolicited connections. While this is useful to a consumer or a business, when used in a server or data center environment, they become chokepoints. All of the requests coming into such a location are unsolicited. This consumes the resources of the firewall, which causes it to fail under the load of the attack, Morales said. Read the rest from SearchSecurity.com