The Microsoft Dynamics Partner Technical Services team offers a series of workshops that are designed to provide participants with the knowledge and practice to learn, deploy, administer and sell Microsoft Dynamics products including Dynamics GP, Dynamics NAV, Dynamics AX, Dynamics CRM and Dynamics SL.

This article contains the list workshops which we offer EXCLUSIVELY for partners, so that they can benefit from these workshops.

Highlights

Choose from any of the topics on any of the Dynamics technologies listed. You can even request for custom workshops which would be personalized and delivered to your team.

Benefits

These sessions would enable you to:

• Learn Microsoft Dynamics products
• Setup and administer Dynamics products effectively and efficiently
• Sell to customers more aggressively
• Customize Dynamics products to suit each organization needs

Delivery mode

These sessions would be delivered remotely over Online Meeting at a convenient time and date to your organization only.

How is it charged

As your company is a Microsoft Partner and you are eligible for a number of benefits, including Partner Advisory Hours, the engagement opportunities can be leveraged by consuming these advisory hours.

Technologies

Please find the details of the various customized one-one consultative workshops which we provide.

• Dynamics AX
• Dynamics CRM
• Dynamics GP
• Dynamics NAV

The pricing model for Dynamics GP 2013 and Dynamics NAV 2013 has changed.

Take a look at the details of the new pricing models in the links below.

Dynamics GP 2013 & NAV 2013 Pricing and Licensing

https://mbs.microsoft.com/partnersource/partneressentials/licensingpolicies/perpetual-licensing.htm

Dynamics GP 2013 & NAV 2013 Licensing Guide

https://mbs.microsoft.com/partnersource/pricing/announcements/MSDNAVGP2013LicensingGuide

Hope this helps.

Take a look at the article published by David, which gives a peek into some of the cool features of Dynamics GP 2013, as they unravel.

http://blogs.msdn.com/b/developingfordynamicsgp/archive/2012/07/27/microsoft-dynamics-gp-2013-feature-of-the-day-week-1.aspx

Keep watching out for more details on other new features in the following weeks.

Anand has posted another article on CRM 4.0 and Sharepoint, where he talks about the concepts of Dynamic Documents.

Take a look at the article in the link below.

SharePoint 2010 and CRM 4 - Dynamic Documents

Hope this helps...

Anand has come up with some cool articles on the following topics, which I am sure will be useful to the community.

Take a look at these articles which are given below.

1. CRM 2011 and SharePoint 2010 Integration - Part 1
2. CRM 2011 and SharePoint 2010 Integration - Part 2
3. CRM 2011 and SharePoint 2010 Integration - Part 2 Continued….
4. FUTURE of CRM 2011 and SharePoint 2010 Integration - Part 3 and Part 4
5. CRM 2011 and SharePoint 2010 Integration - Part 4
6. CRM 2011 and SharePoint 2010 Integration - Part 4 (Enhancements)

Keep watching this blog for more interesting articles coming up...

Sometimes, when we book invoices in payables, we might require distributing the expenses into multiple GL accounts based on business requirements. In most of the situations, a specific purchases account gets defaulted from the vendor (or) from the company posting account setup and the users manually add additional expense lines at the distribution window at the time of transaction entry and apportion the expense to the various expense GL accounts.

This can be quickened, especially if we are able to identify the most common expense heads which get posted into at the time of the payables transaction. Once the accounts are defined, you can enter the various purchases accounts at the Vendor Account Maintenance window, by clicking on the  button near the purchases account description as shown below.

     
When the button is clicked, the Additional Vendor Accounts window is opened where we can enter the additional purchases accounts needed. You can also define these additional purchases accounts at the vendor class level as well. We can also specify which accounts should default on the transaction distribution entry window as well. These additional accounts which have been marked to default will automatically display on the distribution entry window as shown below.

 
The amounts default to 0 for these lines. By default the entire expense amount gets defaulted under one specific purchases account. The user can apportion the amounts to these accounts if necessary (or) leave them as 0 and continue posting the invoice without apportioning. If we leave the additional purchases account as 0, the system ignores those lines during the posting process and only picks the accounts which have an amount associated to it.

This would be really a time saving feature for many of the clients who may be doing this process manually day in and day out.

Smartlist Builder is a great tool to create custom smartlists. We can create smartlists using Dynamics GP tables (or) using SQL objects. However, there have been many requests from customers and partners to retrieve the data from smartlist using a sub query filter. An example of such a request is to pull out all payables transactions with the complete distributions, where specific expense accounts are used. Assuming a
voucher has the following distributions.  

The request is to extract the specific voucher and all its distribution lines if the miscellaneous expenses account was used. This is ideally to analyze the complete distribution in the voucher so that the need for the suspense account can be analyzed. Ideally, for such scenarios, a  SQL query would be the best option. The SQL query typically looks as what is shown below.

SELECT  * FROM   
dbo.PM30600
WHERE   VCHRNMBR IN ( SELECT    VCHRNMBR
                      FROM      dbo.PM30600
                                WHERE     DSTINDX IN
( 167, 256 ) )
                AND
dbo.PM30600.DOCTYPE = 1
ORDER BY dbo.PM30600.VCHRNMBR

We can make use of the “Is Equal To One of List” option and provide a subset of vouchers which need to be returned, but it is not the efficient method of achieving the same, since the filter in the SLB definition needs to be changed every time we run the query to get the appropriate results, which does not make sense. This article explores more into how this functionality can be achieved using Smartlist Builder.

First create an Equals JOIN (there is not Inner Join option in SLB, use Equals) between the PM Distribution History File and the PM Paid Transaction History File with the Voucher Number and Document Type. Then add a restriction on the Distribution Account to be one of the following accounts as seen in the screen shot below.

• 000-6630-00
• 300-6530-00

Note: The restriction has to be applied on the distribution table which has an inner join with the transaction history table and NOT on the one which has the left outer join with the transaction history table.

Now create a LEFT OUTER JOIN between the PM Transaction History File and the PM Distribution History File with the Voucher Number and the Document Type. Display the distribution details (Account Number, Debit Amount and Credit Amount) from this distribution table.  Click on Options and select the option Summary Smartlist and change the Summary Type for the following fields as explained below.

• PM Paid Transaction History File – Voucher Number  – Group By
• PM Paid Transaction History File – Vendor ID – Group By
• PM Paid Transaction History File – Document Type – Group By
• PM Paid Transaction History File – Document Date – Group By 
• PM Paid Transaction History File – Document Number – Group By
• PM Transaction Distribution History (3rd table shown above) – Voucher Number – Group By
• PM Transaction Distribution History (3rd table  shown above) – Distribution Sequence Number – Group By
• PM Transaction Distribution History (3rd table  shown above) – Distribution Account Index – Group By
• PM Transaction Distribution History (3rd table shown above) – Distribution Type – Group By
• PM Paid Transaction History File – Document Amount – Average
• PM Transaction Distribution History (3rd table  shown above) – Debit Amount – Average
• PM Transaction Distribution History (3rd table shown above) – Originating Debit Amount – Average
• PM Transaction Distribution History (3rd table shown above) – Credit Amount – Average
• PM Transaction Distribution History (3rd table shown above) – Originating Credit Amount – Average

This provides the same results that we would have obtained using the SQL query provided above.