Packt’s Microsoft Dynamics Mayhem

Packt Publications has once again given us an opportunity to get desired Microsoft Dynamics books at staggering discounts.

The list of books are quite handful. You do get favorite Microsoft Dynamics GP books (Cookbook by Mark Polino, Reporting by Liley & Duncan & Implementation by Victoria Yudin); all are awesome books for any GPian.

Visit Packt’s page to learn more about this and get benefited: Microsoft Dynamics Mayhem.



RIP Apture – I Will Miss You

How many of my blog readers remember about my blog being enabled with Apture Highlights?

It’s very sad that this beautiful feature is now no more. I got to know this long back, but the feature that I added on my blog still worked; until this morning.

You check out Apture’s Site. All you got to see is a message from Apture Team as below:

I am not sure what to express, but only one thing which I feel right now is this: Google, you have successfully killed one more beautiful product.

RIP Apture. I loved your features. I loved the way you simplified my vocabulary learning. I loved the way you just simply popped out of the web page without taking me to any other site. I loved the way you were just a simple yet catchy product called Apture. I was so in awe that I put your logo on my blog and proudly claimed that my blog got “Aptured”.

Not any more.

I will surely miss you.


To all Budding GP developers – Screen Resolution Does Matter

This is very silly point, but quite a huge dampener when it comes to Customer satisfaction.

I had given a simple customization as a trial to a budding developer as part of an exercise. I received the chunk to test it out.

What I could see was a huge window containing almost 50-75 fields (including labels, several text boxes, etc.) with lot screen real estate being wasted between fields. Secondly, this window went out of my test machine’s screen space. The only possibility for that, in my opinion, is the resolution of the developer’s machine was way too higher than my test machine’s screen resolution.

Always, keep in mind, that when you develop a customization on a computer with higher resolution than that of the customers’, it’s going to be an issue. Customer would have to scroll horizontally each time to enter or view data on each field. And trust me, that’s very irritable than a bad and buggy customization itself.

Always, try to limit the window size that would fit inside a 1024 X 768 screen resolution (that’s the lowest that I feel is still existing in this universe), so it would fit in almost all resolutions.

This possibly be a non-issue soon with technology being so advanced nowadays and customers are willing to shed out some bucks on higher resolution & wide screen monitors.

But you never know.


Welcome 2012…!

My heartfelt wishes to entire GP Community… Happy, Prosperous, Successful & Peaceful 2012…!!!

Most part of 2011 was quite dull, especially the later period, due to various professional and personal commitments. I would like to change it this year and be active as much as possible.

Wishes again for a wonderful 2012.


Taking A Much Needed Break

As you all know by now, I have not been active on my blogging due to a very stringent schedule for past 5 months. And I had been burning my energy for past 2 years without a halt.

Now, I am extremely happy and relieved to have got a much needed break from work and will be going on a vacation for a month from now. I am excited enough to get in touch with my native country and my people. There is long schedule for the next one month; no escape from that. But that’s going to be ALL PERSONAL. Meeting people, visiting places, attending functions. I badly need it.

Does not mean that I will not be keeping touch with Dynamics GP. 🙂 I will certainly be reading all posts from fellow bloggers and will be updating myself with happenings.

Once I am back from my vacation, I assure I would be a hungry soul and be posting on my blog as frequently as it had never been.


Dynamics GP Insights – From BKD Technologies

A new blog out there launched by BKD Technologies which is going to be a dedicated GP blog.

Check out: BKD GP Team Blog – Dynamics GP Insights.


Microsoft KB Articles – Is it really confidential?

I am well aware this post may kick up some controversies. But I honestly do not mind facing that.

Recently one of my contacts asked me about a GP process and asked my help in getting any KB articles related to that process. I said I would share the KB article number with him but since Microsoft says that it is all *confidential*, I cannot distribute the article directly or publish it directly on my website. I also mentioned that he could instead refer to that KB article number and look it up from Microsoft PartnerSource / CustomerSource. After all, I was under the impression that he’s also a Consultant and is working with a Partner, so ideally he has got access to PartnerSource.

After a week, I was quite shocked to know that he later *downloaded* the same KB article from some other website (I do not want to name this website here, as it is also a known Microsoft Dynamics Partner) as a PDF document. And he criticized me for giving him a lame reason for not sharing the article myself. Worst thing, he even accused me of being selfish in keeping information only with me. OK, that’s quite understandable from his side. What I don’t understand now is the term CONFIDENTIAL on all these KB articles.

Microsoft is keep these articles with a confidentiality tag and has given access ONLY via CustomerSource or PartnerSource. But in reality there are many people out there who clearly violates this *confidentiality* part and has published these articles open.

It’s quite simple. I just don’t want to look dumb in front of people when I say “These KB articles are confidential and are NOT supposedly to be distributed openly”. Well I am frankly serious. You feel like you are the most dumbest guy in this world by saying that. Come on, you have these articles openly sprayed out there on several websites (some of them are genuine Microsoft Dynamics Partners) and all you gotta do is to search and download it.

That brings on my mind several questions for Microsoft:

1. What’s the scope of confidentiality for all these KB articles?
2. On what basis this *confidentiality* is defined and when it is considered violated?
3. What is the real point in keeping these articles as confidential, if I can download these articles from anywhere anytime anyhow?
4. Why don’t you just take that *confidential* tag out and keep it open for all, irrespective of whether they have CustomerSource / PartnerSource access?