Visual Studio Tools for Dynamics GP – A Weird Flaw/Limitation


I must first admit that I faced this issue (or may be flaw…!?!?!?!) only now after all these years of VS Tools development expertise.

The issue is this: I want to write a custom code on two events; SOP Entry Print Button and POP Entry Print Button. When I initialise the event method for SOP Entry Print Button, following is how it generates the code:

Snip20130221_4

And the event method gets created as follows (if you use TAB to create the methods automatically):

Snip20130221_5

After above, when I try to initialise an event method for POP Entry Print Button, following is how it generates the code:

Snip20130221_6

When you try to press TAB to create the event method automatically, it takes you to previously created method.

Because, print buttons on both windows (SOP Entry & PO Entry) have same name technically, which is WindowPrint, VS Tools doesn’t understand both are from different windows and it just goes on to refer to one single method instead of two.

But you are not stuck there forever. Simple solution is to manually name your method initialisation with logical names, like below:

Snip20130221_7

And like below:

Snip20130221_8

Visual Studio Tools for Dynamics GP does not restrict you from using only names that it suggest.

VAIDY

Extender Transition Update – From eOne Solutions


eOne Solutions has posted an update on Extender Transition process on their blog. It’s very important for both partners and customers to read it and get an idea about what’s been going on and what to expect in future.

I would like to highlight the points about Pricing Changes, which are highly critical to any customer. Read the post and get informed.

VAIDY

Field Service Setup Menu in Microsoft Dynamics GP 2013


Has anyone noticed a subtle but highly logical change in Microsoft Dynamics GP 2013 menu structure?

Field Service Setup menu was grouped under Project till GP 2010. The path to access Service, Return, Contract setup menus was Microsoft Dynamics GP -> Tools -> Setup -> Project; which quite honestly did not make any sense. You are accessing Field Service setup, but from under the name Project…!?!?!?!?!?

Good folks at MSFT (and/or original developers of Field Service) might have sensed it, so now the setup menu items are logically structured under Field Service.

Snip20130218_1

I am happy to say the least. Because, if you want to access Field Service setup windows from GP home page, it was not possible till GP 2013. Now that’s also been fixed.

Small change, but a BIG difference it has made. Thanks MSFT & Field Service Team, for this.

VAIDY

Importance of PO Line Item Entry Dates


How many of you, PO users, use the following dates on a PO Line Item Detail Entry window in Dynamics GP?

Snip20130216_1

GP defaults all appropriate fields with User Date, but user can change it with actuals.

These dates are not mere dates. They offer critical means to improve vendor followups. And this could be done per PO line item. For instance, you can create a SmartList custom alert and add it on your GP home page (Reminder Cue) for those PO line items whose Current Promised Date is reached & PO line status is not Closed, Received or Cancelled.

It’s a pain, though, to make this dates entry happen. In my case, users always would say that it’s too much of a data entry and they already have something else as followup mechanism. But trust me, they are fooling themselves (first) and the company overall.

VAIDY

Document Attachment in Microsoft Dynamics GP 2013


I am a bit late on this topic. We already have many posts (including Feature of the Day – Inside Microsoft Dynamics GP) on this written by several community members. So instead of repeating it again, I am just adding pointers here to those posts.

To just brief what it is: Document Attachment is a new feature in Microsoft Dynamics GP 2013, which would enhance the way we currently deal with document attachments on a record. If you had sensed it right, yes it’s almost like OLE Notes, but much more than that.

This scores above OLE Notes, purely on grounds of three main factors:

  1. It doesn’t restrict itself to 32 bit architecture, like OLE notes container does.
  2. It is compatible with Web Client, but OLE notes is not.
  3. It stores the attachments on company specific SQL tables. You heard it right. It stores on database by harnessing SQL Server’s file stream, if I am not wrong.

More information about this (and how to use) could be read on below posts:

VAIDY

OLE Notes & GP 2013 Web Client – Mariano


It’s a bit hard to take it, but reality being the OLE Notes attachment feature won’t work on GP 2013 Web Client for current technical reasons.

Read his post here: OLE Notes and Microsoft Dynamics GP 2013 Web Client

That brings to us a new feature called Document Attachment in Dynamics GP 2013. This can be used instead of OLE Notes. It looks just perfect for me to start using it instead of OLE. Not just because of the incompatibility with web client, but also due to it’s robust features.

More can be read in my next post and also Mariano’s.

VAIDY

Microsoft Dynamics GP 2013 – Feature Videos


Awesome way to learn what’s new in Microsoft Dynamics GP 2013.

Inside Microsoft Dynamics GP (official GP blog) has posted a list of all Microsoft Dynamics GP 2013 Feature videos.

I personally checked out some videos and it’s highly informative, but have not gone thru’ the entire collection though.

Go ahead and explore the videos. I am sure you will start planning to optimise some of your business processes after seeing these new features.

VAIDY

Collections Management for Microsoft Dynamics GP Moves Out To Professional Advantage


Microsoft seems to be in a mood to give back all modules to its original developers. First it was Extender, then it was Audit Trails, Electronic Signatures, Risk Management Suite; now it’s the turn of Collections Management.

Errol Schoenfish, on Microsoft Dynamics GP official blog, announces that Collection Management for Microsoft Dynamics GP transits to Professional Advantage; it’s original developers.

Any licensing and module procurement would be affected only from June 1st, 2013. We have both CustomerSource and PartnerSource links to learn more about this transition.

Interesting…

VAIDY

Extender for GP 2013 – Release Postponed


This is, to some extent, bad news for me at least. I was planning for an early upgrade to GP 2013 for my GP production environment. As 40% of my customisation depend on Extender, it feels so bad that I cannot get Extender for GP 2013 till Early to Mid February 2013. This news has been confirmed by eOne Solutions on their official blog.

Original post here: Delivery Date.

I am disappointed to say the least. But considering the issues that eOne developers are going thru’, especially due to a very late announcement from Microsoft to detach Extender from their OEM arrangements, I empathise with them on their most gruelling time to get things streamlined and meet customers’ expectations.

I shall await their official announcement on Extender’s availability for GP 2013.

VAIDY

GP2013 Module Homepage Redesigned


Another important and notable change that we have in GP 2013 is the module homepage being amazingly redesigned, much to users’ delight.

GP2013 Module Homepage Redesigned

 

As compared to previous versions of GP (from 9), what you will see here is the complete menu without any collapse/expand functionality, but with a scrolling option within that small rectangle frame; which means you don’t have to scroll to the bottom of GP itself, but just scroll down within that frame, so you don’t have to scroll up/down to access other frames.

If you are trying to open Receivables Batches, I just have to scroll down on Transactions frame. When I am done, I won’t have to scroll up/down again to reach out to open Receivables Statements.

Cool, isn’t it? If you are heavy user of modules homepage for your day-to-day tasks, this is going to increase your productivity most certainly.

VAIDY