Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Bill Marshall]

One of the new features in GP 2016R2 is the ability to move reconciled transactions to history.  So I’ve been testing this out and have run into an odd issue where, on the Bank Balance window you cannot drill down to the transaction if it’s in history. No error, no message.  It looks like nothing happens, but something does.  I looked at the source code and SQL procedure that builds the temp table and I’m convinced that the code for the Zoom button is not correct, but I’m also not sure because I’m wondering if could be something in my data. I’m just having a hard time believing that they’d make such an obvious error.

So, what happens on that window is that a stored procedure (cmPopulateHistCheckBalanceTemp) builds a temp table from the CM Transaction and CM Transaction History table.  According to the stored procedure, Transactions get a HISTINDX of 0, Historical Transactions get a value of 1.  On the GP window, the Zoom button looks for a HISTINDX of 2. 

Has anyone tried to clear reconciled transactions and run into a problem drilling down on historical bank transactions?

——————————
Bill Marshall
President
mc²
——————————

[Bill Marshall]

I should add that I’ve decided to fix this issue by updating the alternate stored procedure AIT uses to build the temp table, so you won’t have this issue if you’re using AIT, but if you’re finding a similar issue, you’ll need to do something similar.

——————————
Bill Marshall
President
mc²
————————————————————————-

[Rob Klaproth]

That’s great Bill for people using your product, but I would caution against anyone modifying the Microsoft stored procedures.   They should wait for a fix from Microsoft, otherwise they have put their system in an unsupported state.  Given that this is new functionality that users did not have before this should not be too big of an issue, as hopefully you backed up your data before you archived it and can restore from a backup and wait for Microsoft to provide a fix.

Has someone notified microsoft of this bug yet?  If you submit a support case, it will become “non-chargable” if they determine it to be a bug so you will not have to pay.  Quite frankly, I am shocked that the stored proc issue was able to make it past QA. 🙂 

Rob

——Original Message——

I should add that I’ve decided to fix this issue by updating the alternate stored procedure AIT uses to build the temp table, so you won’t have this issue if you’re using AIT, but if you’re finding a similar issue, you’ll need to do something similar.

——————————
Bill Marshall
President
mc²
——————————

[Bill Marshall]

You’re right that modifying a stored procedure is not the recommended path, but this one is pretty straight forward, only impacts a temp table and inquiry, so it’s not messing with the posted accounting data.

I have an unpleasant history with Microsoft regarding support requests that they charge me for and then 12 months later figure out it’s a bug. I’ve discovered way to many to track down when they fix them and am not willing to have them sit on $500 bucks hoping they’ll credit me eventually. I posted in on the Microsoft Community site also, so maybe someone in QA will pick it up there.

——————————
Bill Marshall
President
mc²
————————————————————————-

[Lou Spevack]

You can always post it on Connect.

——————————
Lou Spevack
Systems Accountant | Dynamics Credentialed Professional
American Council on Education
Washington DC
————————————————————————-

[Bill Marshall]

Do you mean the Dynamics community forum managed by Microsoft, or is Connect different?  I put a post on the forum and another consultant confirmed my results.

For those of you who are familiar and comfortable with manually loading a stored procedure, I’ve put together a fix, but it can’t be uploaded as it’s a sql file. If this bug becomes an issue for you, reply to me individually.

Keep in mind, as always, that Microsoft does not support this, nor am recommending this unless you are really confident in your SQL skills and document everything. Any changes you make will be removed if you run a service pack update or create a new company. Note: If Microsoft makes a fix by changing the Dynamics dictionary instead of the stored procedure (as I did), the changes in this fix will revive the issue for you and you will need to revert to the original stored procedure. 

I’m not going to put in a 20 page legal disclaimer, but you get my drift.

——————————
Bill Marshall
President
mc²
————————————————————————-

[Jeff Pfershy]

Thanks Bill for reporting it on Connect. Folks can vote for ID #3116975 here: https://connect.microsoft.com/dynamicssuggestions/Feedback/Details/3116975

——————————
Jeff Pfershy
Solution Consultant
248-489-0707
The TM Group, Inc.
Farmington Hills MI
————————————————————————-