With Extender 2013, we have whole lot of surprises on how it got enhanced. One biggest enhancement/change to Extender is the way it treats Extender Detail Window (that is the name till previous version).
Previous version’s Detail Window definition looked as follows:
Not any more… There is no such option called Detail Window. From now on, every window is called, well simply, a Window.
So where is the option to setup whether it’s a multiple row entry (grid) or not? Here it is:
Just select option “Display scrolling grid” and you are good to go.
Clearly, eOne developers have done an immense cleanup work on Extender’s design. Overall, classification of Extender resources itself is now shrunken as follows:
Interesting changes; I have not gone thru’ all changes/enhancements yet. I will be posting more on all those interesting and critical changes.
So far, thumbs up to eOne Team, for their efforts.
Well, I could understand what you might think after reading the title of this post AND if you had read my previous post on GP 2013 Home Page Redesign.
I did admit that the redesign was kind of great for users. Ian Grieve had commented back with an important #FAIL factor of this redesign.
With that #FAIL factor, I just got one more to crib about. So lets list it:
You cannot scroll within a frame. You MUST rely on mouse clicks(or a trackpad). You have no other option. (Thanks Ian, for your feedback with this point).
If you ever want to realign the frames of a module (for instance Manufacturing), you can. But wait, that would stay ONLY TILL THAT SESSION IS ACTIVE. Once you log out from GP and log on back, your realignment is gone. Poof!!!
I am sure it is going to be highly irritating for users who rely mostly on GP home page.
And with that above statement, I now reverse my opinion on my first post.
That customisation was developed using Modifier with VBA. But with Dynamics GP 2013, much emphasis has been given to the new Web Client. Which means, all our VBA code logic won’t be supported by web client.
That said, I have now converted my code from VBA to VS Tools (using C#.Net as programming language). Those who are interested can download it FOR FREE from following link:
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.
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.
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:
It doesn’t restrict itself to 32 bit architecture, like OLE notes container does.
It is compatible with Web Client, but OLE notes is not.
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:
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.