Kinder Surprise, (or Kinder Egg’s that is also called) is something that most kids loves. Why ? It contains 3 positive elements, and that are (normally) a surprise, chocolate and a toy.
I wanted to create a Kinder Egg function on the PDA, that simplifies 3 tasks into one task. The tasks of my choice was:
1. Set the default issue/receipt warehouse location for an item,
2. Move all on hand of this item into the new location.
3. Adjust/count the new location.
So I created the following PDA screen:
Here the PDA asks for an item barcode, and then the user can scan the new default location, and select if the system should move ALL on-hand to the new location. After the movement has been done, then the PDA will adjust the final quantity in this location. In the background the PDA used standard AX journals.
For smaller companies this truly save time. Just imagine the time you would have to spend to do this using the item warehouse setup, transfer journal and counting journal.
That is Kinder Egg 
Kurt Hatlevik - Dynamics 365 Blog 
Ok, wait a NDA to sign…
Ax 2012 is ok, but we also need a solution for Ax2009. Is it possible to backport this solution to ax2009?
LikeLike
Sorry. We have not plans to support AX 2009.
LikeLike
Ok, we’ll try AX 2012, we wait NDA from you.
LikeLike
Thanks for your reply.
Our company now runs several ax-projects in retail and we are very interested in PDA-solution.
Could you please send me some materials on your solution: price-list, license model, demo version etc.
Also some additional questions:
1. Do you use Ax2009 or Ax2012?
2. One PDA-form can be used from different PDA’s with different resolution and the form will be automatically resized?
Best Regards,
Dmitry.
LikeLike
Hi again. Currently the PDA solution works with Dynamics AX 2012 CU3, CU4 and R2.
In relation to supporting many different screen resolutions, this is quite easy for us to support, but in our demo environment the screensizes are fixed, and defined by a macro.
We do have a program where you can have all available material and also a ready to use VMWare demo environment. All we need is a small signature on a NDA document. I’ll send you this.
LikeLike
Recently I had a discussion with a collegue of mine talking about the best solution to develop
WMS application in AX 2012 (ax form or Visual Studio Forms using services).
Looking your blog (that we appreciate very much) we understand in a different way your approach. Actually while I am thinking you are using standard Ax development (forms builded in AOT by X++ and then used by a remote access), my collegue thinks that your solution is based on .Net forms calling AX services.
Could you please help us solving the debate?
Thanks very much for a suggestion.
Best Regards
Roberto
LikeLike
Hi Roberto. My solution is 100% AX and X++. This gives me the possibility to use all the “goodies” withing AX, and it it actually very fast to create forms and functions. In average I use 8 hours per form/screen, and I have 52 forms so far. And it is now increasing, since we move into Project and Services on the PDA.
LikeLike
Hi Kurt,
you provide very usefull solution…
Could you please answer some questions:
1. Do you use web Forms or common Ax Forms?
2. On your PDA you run Remote Desktop?
3. Which models of PDA is better for your solution (Operations System ans screen Resolution)?
Best Regards,
Dmitry.
LikeLike
Hi Dimitry.
Thanks for you comments. here is my answers :
1. Do you use web Forms or common Ax Forms?
–> I use common AX forms. In this release, the forms are without datasources, and all Logic is inside form-classes. So the form-client is very thin, and not bound to data sources.
2. On your PDA you run Remote Desktop?
–> Currently yes. In the future, the same classes can support HTML5 Clients when the AX7 becommes available.
3. Which models of PDA is better for your solution (Operations System ans screen Resolution)?
–> PDA model is not important. What is important is that it have WIFI, barcode Reader and can do a full screen RDP into the server. The PDA AX-screen sizes is controlled by a set of macro’s, that makes it possible to use larger screen than the recommended 480×640 screen size. The macro also controls font sizes, and the placement of Fields and buttons are automatically sized and positioned in the code.
Take care, and happy Daxing
LikeLike