Dynamic Future - Vote for Features - Historical, Aged Received not Invoiced Report

I'm back with a new feature that I'm hoping you'll vote for. We need a Historical, Aged Received Not Invoiced report for P.O. and receiving clean up.

It's more and more common for auditors to want to know what's in Accrued Purchases and what was there at the end of last month, quarter or year. If you didn't print the report on the exact day they wanted you're stuck.

It's also not unusual to have invoice paid via AP thereby stranding receipts in Accrued Purchases. Without an aging it's really hard to decide that an item is old enough to research. Without a historical option there is no way to really research this over time.

If you want this option, go vote at:

https://connect.microsoft.com/dynamicssuggestions/feedback/details/778666/historical-aged-received-not-invoiced-report

Dynamic Future - Vote - Remove or move the "Human Resources is Registered" message, make Employee Class work for HR Ben/Ded rolldown

This is going to be the last feature recommendation for a little while. With GP 2013 about to release I want to give it time to settle and let people start using it and then we'll get back on the suggestion horse.

This weeks, recommendation is Remove or move the "Human Resources is Registered" message, make Employee Class work for HR Ben/Ded rolldown

This message actually refers specifically to deductions and benefits and how they work when HR is installed. It's not terribly clear and could really be improved. If you think it should be improved too, hit the link and vote.

Dynamic Future - Vote - PSTL Object Initialization

Charles Allen suggest that when the Professional Services Tools Library is initialized for one company it should be available for all companies. It shouldn't have to be initialized for each GP database. If you agree, vote for this suggestion at:

https://connect.microsoft.com/dynamicssuggestions/feedback/details/770383/professional-services-tools-library-object-initialization

Dynamic Future - Vote - GP HR Track History on Term/Rehire

Carol Livingston thinks that it would be a great idea if GP HR would keep history when rehiring an employee. I couldn't agree more. If you thing so too, go vote at:

https://connect.microsoft.com/dynamicssuggestions/feedback/details/613682/gp-ms-dynamics-gp-human-resources-track-history-on-termination-rehire-dates

DynamicFuture - Vote - Dynamics GP Code Names

 

The current Dynamics GP code names for upcoming release are boring. GP '15' just doesn't have a lot of zing so I've posted an MS Connect suggestion around code names. I think they should use breakfast foods like crispy bacon or biscuits and gravy as code names. Google uses dessert items for Android updates. I think people should start their day with the Dynamics GP Crispy Bacon release.

 

If you agree, vote at: https://connect.microsoft.com/dynamicssuggestions/feedback/details/768714/dynamics-gp-code-names



 

DynamicFuture - Vote - Release the Field Service Web Client Sooner

I like this suggestion so much, I moved it up in the rotation. Michelle Kocher suggests that Microsoft move up the release of the web client for Field Service. She make a great point. Field Service users are in a unique position to get huge benefits from a web client since many of their user are remote. (That's pretty much the definition of field service.)

 

If you want to crank up the release of the web client for Field Service go and vote at:

 

https://connect.microsoft.com/dynamicssuggestions/feedback/details/768288/gp2013-web-client-for-field-service

 

 

Dynamic Future - Vote - Credit Card Payables Run

The latest suggested improvement to Dynamics GP is to allow an AP check run but using credit cards as the payment method instead of issuing checks.

If this seems like something you want to see, vote here: https://connect.microsoft.com/dynamicssuggestions/feedback/details/763004/perform-a-credit-card-run-just-like-a-check-run

Dynamic Future - Vote - Never Forget to Match that Purchase Order

Another great suggestion from Leslie Vail. How about a an option in AP to identify open P.O.'s/Receipts when trying to enter an invoice for a particular vendor?

If you like this idea, vote for it at: https://connect.microsoft.com/dynamicssuggestions/feedback/details/669719/gp-never-forget-to-match-that-purchase-order-again

Dynamic Future - Vote - Run PSTL as a non 'sa' user.

This is one of Leslie Vail's great suggestions. The Professional Service Tools are now free to GP users. However, some tools still require the use of 'sa' and that presents a problem in secure environments. I understand why some tools require this based on what they are doing behind the scenes (like the tools to temporarily disable databases) but we need the requirement for sa' to be minimized. If you want PSTL to not use 'sa' please vote.

Dynamic Future - An Imagined Conversation Around GP 2013 New Features

I'm working through new stuff in GP 2013 as part of my joint session with Errol tomorrow and frankly, all of my favorite new features won't fit in the time that I have to present. I figured most users wouldn't mine if went a little long, by like 3 hours, but 'they' said no, I have to choose. It's not quite like choosing between my children because let's face it, buying Dynamics GP is way cheaper and less smelly than having a child, I mean a teenager but and infant could work too there I guess. But I digress.

I'm skipping the vote this week to reflect on all of the cool stuff we asked for that made it into GP 2013. Things like depreciation undo, printer selection, P.O. prepayments and clearing unit accounts at year end. Oh and there is better SSRS integration and tolerance handling and...there I go again. So I thought that I would leave you with a short tale (I mean story, tail is the thing that wags) that I'm certain, is probably not very true, mostly.

This conversation almost certainly didn't take place in a unnamed hallway in an out of way building on Microsoft's Fargo campus between an unnamed program manager and an generic Dexterity developer, when Dynamics GP 2013 was merely a gleam in Marketing's eye.

Program Manager: So the world is moving to the cloud and so are we. We need to make the future of Dynamics GP cloudy.

Developer: Um, you mean like MAS 90?

Program Manager: No, I mean that we have to build a web client for the next version of Dynamics GP.

Developer: Funny you should mention that. In what little work time I have left after reading all of Mark Polino's blog posts every day, I had lunch with a robot space alien that gave me a magical box that turns Dexterity into HTML...or maybe I wrote it myself and you're just not paying me enough. Either way, I live in Fargo so it's all good, eh.

Program Manager: That's great! But we can't just ship a web client. Users will want more than that. It's not like we're Oracle and we can keep raising enhancement fees without delivering any value. Besides, Polino already suspects that Musgrave uses alien technology for the Support Debugging Tool. We're going to need to add more features as a diversion. But where do we get them from?

Developer: Hey, what about Microsoft Connect? You know, that website where users can suggest and vote on new feature for the next release of Dynamics GP.

Program Manager: I keep talking about that but I didn't know that anyone actually uses it. Dust that off and see what you can find. I know that we need some Fixed Asset stuff. People whine at me about Fixed Assets all the time. Maybe some more reporting thingies. Reporting is like Chinese food. People want more 20 minutes after you give them something great. Oh and we need name for the new product. Something Marketing can't say no to. Maybe 'Dynamics GP Super ERP Software of Greatness...with Bacon'? You can never go wrong with bacon.

------------

This was definetly, assuredly not how Microsoft Dynamics GP 2013 probably got all of those great new features that we've been asking for.

Dynamic Future - Vote - Assign an item to all Sites

Leslie Vail has a new suggestion for Dynamics GP and I like it well enough to hop on the bandwagon. As she explains:

Microsoft Dynamics GP is supposed to support multi-site operations, yet it's distribution module doesn't allow for it. One example is that I can assign all items to a single site, but I cannot assign all sites to an item.

I want to be able to assign all sites to an item. If you want this too, go vote at:


https://connect.microsoft.com/dynamicssuggestions/feedback/details/763003/assign-an-item-to-all-sites#tabs

Dynamic Future - Vote - Payroll Sorting

How would you like some better sorting on the Payroll Transaction Entry Window? That's the subject of this week's suggested improvement to Dynamics GP. If you like this, vote at: https://connect.microsoft.com/dynamicssuggestions/feedback/details/480852/gp-implementer

Future Dynamic-Vote-Batch Approval for POP Batches

So I've gone to something straightforward this week. I think that POP batches, Receiving, Shipment Invoice and Invoice batches should have batch approval functionality similar to AP. In the case of Shipment Invoices and Invoices in particular, these actually create AP batches and sometimes AP wants/needs to control the posting.

I know, the approval should really be at the P.O. level but since you can over/under receive and change the cost (depending on settings) some companies want a double check before sending this to payroll. If you'd like to vote for this go to:

https://connect.microsoft.com/dynamicssuggestions/feedback/details/760005/pop-invoice-match-batch-approval

Dynamic Future - Vote - Dependent Address Rolldown

This is a nice HR/Payroll suggestion, dependent addresses should roll down by defaul from the employee's address. Yes this won't always be the case but I'm willing to bet that it's the case more than half the time so there really should be an option to handle this better than retyping the addresses.

Apparently I left off the link. You can vote at: https://connect.microsoft.com/dynamicssuggestions/feedback/details/567286/gp-dependent-address

Dynamic Future - Vote -

John Lowther wants additional payroll account options. If you want that too, go vote.

For any Payroll Account Type you only have the options for Department, Position, and Code to map that to a specific posting account.

But I need other items from the Employee Maintenance window like Division, Location, and Class ID, even one of these would solve my problem but all three would be great. Additionally, for existing customers that do not need these extra columns the "All" entry in that column would work fine for them.

Dynamic Future - Vote - Allow bank transactions through the intercompany module

We're going back to banking for this week's new feature that we want to see in Dynamics GP - Intercompany Bank Transactions. This is something I would really like to see in GP. If you agree, please follow the link to vote.

Dynamic Future - Vote - Multicurrency Cash Flow Forecast

Yes, I'm a day late with this. Deal with it, my schedule is a mess.

In this weeks Connect feature, we suggest adding Multicurrency Cash Flow Forecast into Dynamics GP.

It's hard enough to get cash flow forecasts right. I don't even want to think about doing it in other currencies.

Dynamic Future - Vote - Better Control of SmartList Visibility

This feature is my suggestion and it should be easy to implement. I want the ability to control the default visibility of a new SmartList Favorite. Today it defaults to System (all companies, all users). I want the ability to default that to "User" to help reduce SmartList sprawl. I've been recommending the use of "User" for a while now. Especially after a number of companies have asked if it's possible to just delete all the Favorites and start over.

If you want better control of the default SmartList Favorite visibility vote now.

Dynamic Future - Vote - Roll Down Account Segment Description Changes to the Chart

Just to make sure that everyone is clear. You don't have to like these suggestions. If you don't like them, don't vote. However, If you do like a suggestion and you don't vote, you lose your right to complain about that issue.

The goal is to get you thinking, and voting, about what you want in Dynamics GP in the future.

This week's suggestion revolves around the chart of accounts. If you use segment descriptions and allow them to populate the chart descriptions you can get a really clean chart of accounts. But what happens if something changes? For example, you thought that a main segment description of "Receivables, Accounts" was a good idea until you realized that now no one can ever find the account by description. Users are disgruntled, the natives have pitchforks in their cubes. Today you have to go to each account and fix it or use SQL to clean things up. It would be pretty cool if you could change the segment description and have it roll down to the chart.

Dynamic Future - Vote - Multiple Company Support in a Single GP Database

This week's GP suggestion is a big one...Adding Multiple Company Support to a Single GP Database. This request seems to be coming up more often lately. There are third party solutions that can effectively accomplish this but they often change the way that Dynamics GP works. This suggestion is to add Multiple Company support natively in a single GP database.