In Dynamics GP the inventory quantity allocated has a field name of “ATYALLOC”. You can see it lurking in IV00102 table, as a decimal (19,5).
Why is is named ATYALLOC?
A field typed day in and day out, I ponder each time it is why it was named so. After all, would we not expect it to be named “QTYALLOC”, so tell me where did that “A” come from?
My horrific assumption is that this was a typo, the Q and A key on a keyboard being so close together, please let me be wrong. Did such an error get through QA back in the dark days of software development?
I have the feeling there may be a back story to this naming that someone on the inside may be able to tell us about. Perhaps there was a conflict with another field, or some obscure reason it was named so?
Please comment if you can add anything to this mystery…or simply that I’m stupid for not seeing some obvious reason!
Today at m-hance customer day there was a session titled “Joining Information,New Microsoft GP User Group”, hosted by Andy Brown of m-hance.
This session was short, at half hour with an open questions to the audience.
The questions were on purpose seeing formative views along the lines:
- Do the people present think that a GP user group is a good idea?
- If so what should that User Group look like?
- Who should run it?
- Should it be independent of partners
- What would it offer to members?
At this time September 2015, I am unaware of any UK user groups for Dynamics GP. In the US, there is GPUG (GP User Group) a user group that is strong enough to hold a conference each year in the US. It is supported by Dynamic Communities an organisation from that describes itself as…
Dynamic Communities Inc. is the administrative organization behind professional associations and software user groups such as the Dynamics AX User Group (AXUG), the Dynamics GP User Group (GPUG), the Dynamics CRM User Group (CRMUG), and the Dynamics NAV User Group (NAVUG).
Should Dynamic Communities be approached to help?
m-hance would consider helping with seeding a new user group, supporting it to get it going, after all it is in their benefit to grow a strong user community that shines and evangelises the product. It could be just a user group affiliated with that single partner, but an independent user group seems like a much better proposition, one in a position to encompass all the users of GP across all partners in the UK. Any sponsors would find an partner agnostic group spanning all users a more tempting proposition, I would imagine.
Data protection prevents partners passing on customer details, but they can promote such a user group’s existence in say email communications with their customers, thus drive users to such a group.
A show of hands showed half the audience to be interested, however my personal view is that each of those who were interested had a different idea of what a user group should look like to them. There was no firm conclusion.
I would be interested in any comments against this post from people who have touched GP user groups in other territories and how they work there, and what they get out of them.
This may not just be windows 10, some searching turns up reports from Windows 7 onward.
On the desktop machine in question, holding the SHIFT key on the keyboard, causes windows 10 to stick or hold the shift key down even once the key is comes back up. This results in when typing top row numbers, punctuation is typed. Pressing the return key is like pressing shift return. This “feels like” this was the accessibility feature, sticky keys kicking in.
Checking with the Ease of Access Center, it seemed sticky keys was off.
Time for the old trick of turn it on and off, so check all the check boxes in that section, after clicking on the “Set up Sticky Keys” hyperlink.
Then click “Apply” and then unchecked all the boxes and click “Apply”.
Testing should show that holding the shift key for five seconds no longer locks the shift key.
I was wrong, this turns out to be actually to do with the keyboard hardware itself sleeping after four seconds.The keyboard then gets into a logic mess, latching the shift key. The keyboard LED goes out as it goes to sleep, after that the keyboard will then have a latched shift key.
Luckily the solution has been found on you tube, watch the video then find the solution in the comments of the video on you tube. (Basically go to power management tab in device manager for the USB input device (not the keyboard itself) and uncheck the checkbox so don't allow it to be turned off.
Andrew Hayward keynote the m-hance conference earlier in the year
It being late December I’m reflecting on the year, one of the highlights for me was when I got the pleasure of a long chat, one to one, with Chad Sogge & Daryl Anderson and then a quick chat to Errol Schoenfish. I came away having learnt many things that have really changed my whole opinion of the Dynamics GP product future.
The move to service orientated architecture in GP 2015 version is perfect for developers, as is the tighter integration with .NET from Dexterity. This really does open up the product to do virtually anything we can dream up. In my view, this is a really significant moment in the evolution of GP. Today it can now leverage the investment Microsoft has made with the .NET framework and the full Microsoft product stack, including cloud computing.
I also observe Microsoft handing back third party products to the original developers and simultaneously unzipping the core product for more developers to build awesome things upon it. To me this feels like a message that – hey, we can’t be everything to everyone and also keep it all maintained and yet still drive the product forward, it’s time to let you do that for us. Microsoft have a growing ISV community around that can build great things for specific market verticals, thus allowing Microsoft to maintain the framework, core product, adding new features and performance… boy so many features have been delivered recently! The agile development burndown cadence MS have at the moment is really swelling the bullet points in the sales datasheets and giving us plenty of “new toys” to implement!
I do think there are some amazing years ahead of us in the Dynamics world, presenting many opportunities for the ISV community to grow and build some great products on top of our Fargo friends hard work! I can’t wait to see what the next year brings on.