Page 1 of 2612345678910...2025...Last »

Dynamics GP 2015 – Printing Arabic Text

If you are planning to upgrade to GP 2015 and currently having Arabic text in your database need to be printed using report writer, make sure NOT TO UPGRADE to GP 2015.

Normally for printing Arabic text in report writer, if your keyboard was language the text will be displayed as rubbish data as below:

In order to get this printed properly, we used to switch the keyboard language to Arabic and the text will back to normal as below:

However for GP 2015, the system will automatically switch the keyboard language to English upon the generation of the report, and unfortunately the same switch is occurred upon hitting the print button, therefore the Arabic text will never be printed in Arabic and customers will start nagging!

Hope that Microsoft could resolve this soon!


Regards,


Mohammad R. Daoud MVP – MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 – 79 – 999 65 85
me@mohdaoud.com
http://www.di.jo

See original article:
Dynamics GP 2015 – Printing Arabic Text

February 1, 2015 ·  · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 42

The Great Plains Wall of Fame

I have a 3 week, all expenses paid vacation in Fargo, ND in January at the Microsoft offices, learning some of the finer points of Dynamics AX.  As such, I thought I’d share some of the remarkable sights here.  These two walls, in the hallway as you enter the Horizon Building from the Vista Building on the Microsoft Campus, display an interesting collection of news articles from the early days of Great Plains, up through when Microsoft bought the company in 2001.  Pretty cool to take in the history of the application that so many of us have based careers on.

* Click on either image to enlarge

Thanks Doug Burgum!

More:
The Great Plains Wall of Fame

January 21, 2015 · Frank Hamelly MCP-GP MCT MVP · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 30

SOP Quick Print feature does not work when window ribbons are enabled

Happy New Year!! Hope all of you had a great time with family and friends and that you are back getting used to the daily grind once more.

Today, I want to kick off the year with an issue in Sales Transaction Entry window related to the cool ribbons implemented since Microsoft Dynamics GP 2013 R2. By now, you are probably getting used to the absolutely gorgeous user interface which features Microsoft Office style ribbons on every window. Furthermore, you probably already know that the use of such ribbons is actually customizable and in many ways optional – albeit being the default configuration – as described by fellow Microsoft Dynamics GP MVP, Leslie Vail in her article GP 2013 R2 Ribbons. As it turns out, there’s a Dex.ini switch, EnableWCRibbons=FALSE, that controls whether ribbons are enabled within Microsoft Dynamics GP or not. When ribbons are enabled, users can further customize the appearance of the action pane or return to the traditional menu bar for each window.

User Preferences window

Yesteryear (2009), I wrote an article talking about The wonders of CTRL+Q: saving and printing SOP documents in one step and how the Quick Print feature made life easier to the poor souls out there who needed a quick shortcut to printing SOP documents from the Sales Transaction Entry window. In that article I detailed the mechanics behind the feature, written by my good friend David Musgrave.

As fortune would have it, when ribbons are enabled and you are either using the Action Pane or the Action Pane Strip layouts, the Quick Print feature does not work. However, if the User Preference is returned to Menu Bar (you will need to exit Dynamics GP and re-launch for the changes to take effect), the Quick Print option (and CTRL+Q keyboard combination) works just fine.

While clearly an inconvenience, this can hardly be labeled a bug since the feature is still present within the application when the Window Command Display setting is set to Menu Bar as part of the user preferences. It would be nice, however, to have this fixed for Dynamics GP in desktop client mode. I can see how this may or may not work under web client mode as the browser keyboard shortcut combinations take precedence over the application’s shortcuts.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

Read more here:
SOP Quick Print feature does not work when window ribbons are enabled

January 7, 2015 · Mariano Gomez · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 34

Second reason to attend Microsoft Dynamics Convergence 2015: OneRepublic

If you enjoyed the concert last year with Fun (see Microsoft Dynamics Convergence Atlanta 2014 – Day 3) you will be more than happy to know that OneRepublic — not a typo — has accepted Microsoft’s invitation to entertain the attending Convergence 2015 crowd.  

OneRepublic – From left to right: Eddie Fisher, Zack Filkins, Ryan Tedder, Brent Kutzle, and Drew Brown

OneRepublic is an American pop rock band formed in 2002 by Ryan Tedder and Zack Filkins. Originally signed with Velvet Hammer, an outfit under the Columbia Records umbrella, they were dropped 2 months before the debut of their first album.

They successfully released their debut set Dreaming Out Loud in 2007. The album included the smash single “Apologize,” mixed by Timbaland, which shattered digital sales and airplay records worldwide and received a Grammy nomination. The band’s sophomore album, 2009’s Waking Up, produced three singles: “All the Right Moves,” “Secrets” and “Good Life.” OneRepublic released their third studio album, Native, in March 2013 where it debuted at No. 4 on the Billboard Top 200 chart. The set includes hits “If I Lose Myself,” “Feel Again,” “Counting Stars,” “Love Runs Out” and “I Lived.” OneRepublic spent most of 2014 on the road headlining their Native Summer Tour and touring Europe.

This is an inside look at Native Summer Tour.

So, what are you waiting on? Register now for Convergence 2015 and come enjoy a night out with one of today’s hottest bands.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

Read More:
Second reason to attend Microsoft Dynamics Convergence 2015: OneRepublic

December 22, 2014 · Mariano Gomez · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 47

Microsoft Dynamics GP backups with Windows Azure Blob Storage Service – Follow up

As a follow up to my post yesterday (see Microsoft Dynamics GP backups with Windows Azure Blob Storage Service), an issue has been identified with Microsoft Dynamics GP 2015 running on SQL Server 2014 when choosing Microsoft Azure storage as the destination for the backup.

You will receive the following warning message:

The SQL Server version that you are using does not support backing up or restoring your database from Microsoft Azure storage.

I have traced the issue back to the logic in the ‘(L) RGRestoreBackupOption’ of window BackupRestore of form syBackupRestore field change script, which seems to compare the build number even after it has determined the version number is greater than SQL Server 2012 SP1 CU2 (11.0.3339). Of course, the build number for SQL Server 2014 CU4 is 12.0.2430. Since 2430 is not greater than 3339, the script sets the validation flag to false, causing the script to abort with the message indicated above.

This problem is exclusive to Microsoft Dynamics GP 2015 RTM (14.00.0524) running on SQL Server 2014, and cannot be replicated if you are running Microsoft Dynamics GP 2013 R2 or Microsoft Dynamics GP 2015 on SQL Server 2012 SP1 CU2 or greater. Microsoft is currently aware of this situation (at least via the Dynamics GP Online Partner Technical Community Forum), but if you are

For more information on SQL Server 2014 build numbers, see Microsoft Support kb article 2936603, SQL Server 2014 build versions.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

View article:
Microsoft Dynamics GP backups with Windows Azure Blob Storage Service – Follow up

December 15, 2014 · Mariano Gomez · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 47

Working with Dex.ini Settings to customize the Microsoft Dynamics GP Connect gadget

I take a pause in my Microsoft Dynamics GP 2015 Developer’s preview series to bring something fun before the Thanksgiving holiday here in the United States. Hopefully you find this trick very cool and enjoy it in your workplace.


Have you ever wanted to wake up with The Dynamics GP Blogster page as the centerpiece of your Microsoft Dynamics GP application homepage? Or how about your favorite online news outlet? What if you just want to display your company web page or an intranet portal to allow employees to update their information or view the latest company news?

Today I will show you how to take advantage of two obscure Dex.ini settings to customize the Connect gadget.

The standard Connect gadget displays Microsoft Dynamics Community news and updates, but there are two Dex.ini keys used to enable runtime debugging of the Connect gadget. One of the Dex.ini keys turns on the debugging feature and the other allows you to specify a URL to be displayed. The keys are:

DebugConnect=TRUE
ConnectTestURL=http://dynamicsgpblogster.blogspot.com

If you add these two keys to your Dex.ini file and re-launch Microsoft Dynamics GP the result will jump right at you.

Customized Connect Gadget

I also noticed that if the customized URL contains videos, these will play fine within the Connect gadget. How about that for some educational YouTube videos from the Microsoft Dynamics Channel? I tested it in the Web Client and it also worked just fine.

Please send in your comments as I would like to hear how you plan to use these new settings. Also remember, if you are using the Support Debugging Tool, you can roll out the settings to every user without having to visit their workstations.


Take a look at the following related articles:

Working with the Dex.ini Settings in Microsoft Dynamics GP 2013
More DEX.INI Settings!

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

Original post:
Working with Dex.ini Settings to customize the Microsoft Dynamics GP Connect gadget

November 26, 2014 · Mariano Gomez · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 61

Microsoft Dynamics GP 2015 Developer’s Preview: Dexterity Service Patterns – Part 4

What a week of learning that reIMAGINE 2014 conference was! If you stayed for the post conference training classes, even more power to you.

In my previous article (see Microsoft Dynamics GP 2015 Developer’s Preview: .NET Framework Interoperability – Part 3), I talked about the .NET interop capabilities introduced in this iteration of Dexterity and how these new capabilities have become the foundation for unlimited extensibility options for Dexterity-based applications. Today, I wanted to talk about another aspect brought by .NET interop: Dexterity services. However, to understand Dexterity services, we must first take a look at the service implementation patterns.

Wrapped Window Pattern

Under the wrapped window pattern,  a complete Dexterity form or window logic is wrapped into a service. The goal is to instrument the user interface and leverage all the existing validation logic within a RESTful service as to avoid recreating that same logic separately — similar to the behavior displayed by the Web Client.

Wrapped Window Pattern (click on image to enlarge)

A closer to home example is how Integration Manager’s standard adapter leverages the UI to get data into Microsoft Dynamics GP.

Wrapped Window Pattern Considerations

Create .NET object
The basic idea here is to leverage .NET to create a class library with all the properties reflected by the associated Dexterity table, i.e., RM_Customer_MSTR, then expose that class to your Dexterity application (via .NET interop). You can then instantiate that class in Dexterity to map the UI fields to the instantiated class properties. Here are some basic steps to follow:

  • Include all fields from table as part of the .NET class 
  • Remove white spaces from names, i.e., ‘Customer Number’ should be defined as CustomerNumber within the .NET class 
  • Create enumerations for radio groups and drop down lists

Preparation for window being wrapped
What we are trying to do in this instance is, identify all modal dialog elements in our code that may require branching logic for when our application is running in service mode, finding an effective way to handle these.

  • Handle calls to Warning_Dialogs by evaluating service mode state with IsServiceMode() function.
    Warning_Dialogs handling
  • Ask messages for actions need a predetermined action 
    Ask() function
  • On-the-fly record events cannot be performed . When in service mode, if the record is not found, a trace event is created.
Ask() on-the-fly record add
  • TraceAdd and Trace are used to report service events to calling applications or services.


Decoupled Logic Pattern

The Decoupled Logic pattern exposes Dexterity procedures and functions as a service, this is, the business logic does not reside in a form. Under this approach, the objective is to separate the business logic from the user interface. Since we are dealing with procedures and not the user interface, the decoupled logic pattern can be considerably faster from a service performance perspective.

Decoupled Logic Pattern (click on image to enlarge)

Using our closer to home example, think of Integration Manager’s eConnect adapter, which leverages the eConnect assembly and stored procedures to bypass the user interface. At the same time, this is a prime example as to why you want to find a Dexterity pattern approach that’s suitable for creating a service — you may not want to have to refactor the entire UI, depending on the complexity of the UI validations. Key points in determining whether to refactor the UI or not are the frequency of use of the UI in question and performance of the UI code.

Decoupled Logic Considerations

  • In decoupled logic mode, there is no implicit data types validation or conversion. Unlike the Window Wrapped pattern where the map statement manages casing, signed versus unsigned precision, and nulls during the binding of window fields to our instantiated class properties; in the Decoupled Logic pattern we must perform all the conversion and validations.
  • Check for valid value for decimals
  • Check for a valid value for a drop-down or radio group
  • Force strings to upper case as needed, for example, items, customers, vendors, etc.
  • Set default values as needed as user may pass a null value as a parameter to a service procedure

In the interest of clarity (and space), I will tackle some decoupled logic sample code in a follow up article.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

More here:
Microsoft Dynamics GP 2015 Developer’s Preview: Dexterity Service Patterns – Part 4

November 25, 2014 · Mariano Gomez · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 94