Bank Transaction Entry Zoom pulling up wrong check

(0) Share

Report

Posted on by Community Member Microsoft Employee

We are using GP 2010 GP4 and experiencing a very odd issue with pulling up check details. Our payroll department used the same check numbers in recent checks that they also used back in 2008. When we do a Checkbook Register Inquiry for a check number w/ a duplicate (76564), it pulls up both checks properly. But when our Finance Director clicks on the bottom entry dated 01/24/2014, it pulls up the details of the check dated 07/03/2008 in the Bank Transaction Entry Zoom window. If I login as SA on his machine, it does the same exact thing.

However, if we RDP to the GP server and login to GP using our respective usernames, it works just fine. It also works fine if he uses SmartList to view the check.

Any ideas where the issue might lie? Thanks.

*This post is locked for comments

All responses (9)

Answers (0)

Lyn Barr on at

Like (0)

Report

RE: Bank Transaction Entry Zoom pulling up wrong check

Oh, Leslie, great idea! Such a simple fix. Thanks for your input.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Bank Transaction Entry Zoom pulling up wrong check

Thank you for the response. Any info is good info. I am going to see if we need check info from 2008 in the first place. If we don't, I can simply delete any dup check older than x years.
L Vail 65,271 on at

Like (1)

Report

RE: Bank Transaction Entry Zoom pulling up wrong check

Hi,

This also has happened to me a couple of times in payroll when the same check number was used. The checks were separated by years, but when I tried to pull up the details it didn't work. It came up because we needed to void the more recent check, but we couldn't get it to pull up. What I ended up doing is going out to SQL and changing the original check and document numbers. This removed the duplication. I voided the new check and then went back into SQL and changed back the fields I modified. It's not exactly what you are experiencing, but it's similar enough I think. Not sure how this could point to any kind of fix for you, but it doesn't hurt to pass along the information.

Kind regards,

Leslie
Community Member Microsoft Employee on at

Like (0)

Report

RE: Bank Transaction Entry Zoom pulling up wrong check

Here's the DEXSQL.log for the non-working machine when I simply clicked "Number" on the Checkbook Register Inquiry window. Clicking "Number" then opened the Bank Transaction Entry Zoom window:

/* Date: 07/31/2015 Time: 13:14:05

stmt(52776288):*/
SELECT TOP 25 CMRECNUM,sRecNum,RCRDSTTS,CHEKBKID,CMTrxNum,CMTrxType,TRXDATE,GLPOSTDT,TRXAMNT,CURNCYID,CMLinkID,paidtorcvdfrom,DSCRIPTN,Recond,RECONUM,ClrdAmt,clearedate,VOIDED,VOIDDATE,VOIDPDATE,VOIDDESC,NOTEINDX,AUDITTRAIL,DEPTYPE,SOURCDOC,SRCDOCTYP,SRCDOCNUM,POSTEDDT,PTDUSRID,MODIFDT,MDFUSRID,USERDEF1,USERDEF2,ORIGAMT,Checkbook_Amount,RATETPID,EXGTBLID,XCHGRATE,EXCHDATE,TIME1,RTCLCMTD,EXPNDATE,CURRNIDX,DECPLCUR,DENXRATE,MCTRXSTT,Xfr_Record_Number,EFTFLAG,DEX_ROW_ID FROM COM.dbo.CM20200 WITH ( NOLOCK) WHERE CHEKBKID = 'PAYROLL-CHK' AND CMTrxNum >= '76564' AND CMTrxNum <= '76564' AND CMRECNUM = 278716.00000 ORDER BY CMRECNUM ASC

/* Date: 07/31/2015 Time: 13:14:05
stmt(52771440):*/
SELECT TOP 25 CMSortType,CMTrxType,DOCTYNAM,DOCABREV,DEX_ROW_ID FROM COM.dbo.CM40101 WITH ( NOLOCK) WHERE CMTrxType = 3 ORDER BY CMTrxType ASC

/* Date: 07/31/2015 Time: 13:14:05
stmt(52776288):*/
SELECT TOP 25 CMRECNUM,sRecNum,RCRDSTTS,CHEKBKID,CMTrxNum,CMTrxType,TRXDATE,GLPOSTDT,TRXAMNT,CURNCYID,CMLinkID,paidtorcvdfrom,DSCRIPTN,Recond,RECONUM,ClrdAmt,clearedate,VOIDED,VOIDDATE,VOIDPDATE,VOIDDESC,NOTEINDX,AUDITTRAIL,DEPTYPE,SOURCDOC,SRCDOCTYP,SRCDOCNUM,POSTEDDT,PTDUSRID,MODIFDT,MDFUSRID,USERDEF1,USERDEF2,ORIGAMT,Checkbook_Amount,RATETPID,EXGTBLID,XCHGRATE,EXCHDATE,TIME1,RTCLCMTD,EXPNDATE,CURRNIDX,DECPLCUR,DENXRATE,MCTRXSTT,Xfr_Record_Number,EFTFLAG,DEX_ROW_ID FROM COM.dbo.CM20200 WITH ( NOLOCK) WHERE CHEKBKID = 'PAYROLL-CHK' AND CMTrxNum >= '76564' AND CMTrxNum <= '76564' AND CHEKBKID = 'PAYROLL-CHK' AND CMTrxNum = '76564' AND CMTrxType = 3 ORDER BY CHEKBKID ASC ,CMTrxNum ASC ,CMTrxType ASC ,DEX_ROW_ID ASC

/* Date: 07/31/2015 Time: 13:14:05
stmt(52807984):*/
{ CALL DYNAMICS.dbo.zDP_SY02100SS_1 ( 2, 2404, 3, 0 ) }
/*
/* Date: 07/31/2015 Time: 13:14:05
SQLSTATE:(S0022) Native Err:(207) stmt(52764168):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid column name 'desSPRkmhBBCreh'.*/
/*
/* Date: 07/31/2015 Time: 13:14:05
SQLSTATE:(00000) Native Err:(207) stmt(52764168):*/
*/
/*
/* Date: 07/31/2015 Time: 13:14:05
SQLSTATE:(00000) Native Err:(207) status(41):*/
SWSTATUS DUMP*/

/* Date: 07/31/2015 Time: 13:14:05
stmt(52774672):*/
{ CALL COM.dbo.zDP_ME27601SS_1 ( 'PAYROLL-CHK' ) }

And now here's the DEXSQL.log from the working machine ... it's 24 lines shorter:

/* Date: 07/31/2015 Time: 13:14:56
stmt(12232168):*/
SELECT TOP 25 CMRECNUM,sRecNum,RCRDSTTS,CHEKBKID,CMTrxNum,CMTrxType,TRXDATE,GLPOSTDT,TRXAMNT,CURNCYID,CMLinkID,paidtorcvdfrom,DSCRIPTN,Recond,RECONUM,ClrdAmt,clearedate,VOIDED,VOIDDATE,VOIDPDATE,VOIDDESC,NOTEINDX,AUDITTRAIL,DEPTYPE,SOURCDOC,SRCDOCTYP,SRCDOCNUM,POSTEDDT,PTDUSRID,MODIFDT,MDFUSRID,USERDEF1,USERDEF2,ORIGAMT,Checkbook_Amount,RATETPID,EXGTBLID,XCHGRATE,EXCHDATE,TIME1,RTCLCMTD,EXPNDATE,CURRNIDX,DECPLCUR,DENXRATE,MCTRXSTT,Xfr_Record_Number,EFTFLAG,DEX_ROW_ID FROM COM.dbo.CM20200 WITH ( NOLOCK) WHERE CHEKBKID = 'PAYROLL-CHK' AND CMTrxNum >= '76564' AND CMTrxNum <= '76564' AND CMRECNUM = 278716.00000 ORDER BY CMRECNUM ASC

/* Date: 07/31/2015 Time: 13:14:56
stmt(12232976):*/
SELECT TOP 25 CMSortType,CMTrxType,DOCTYNAM,DOCABREV,DEX_ROW_ID FROM COM.dbo.CM40101 WITH ( NOLOCK) WHERE CMTrxType = 3 ORDER BY CMTrxType ASC

I found this link that explains it might be a security issue, but then again, if the user logs into the Production server, it works fine:

https://community.dynamics.com/gp/f/32/t/105143
Lyn Barr on at

Like (0)

Report

RE: Bank Transaction Entry Zoom pulling up wrong check

Forms are basically groups of related windows, and windows are the individual screens(windows). The CM_Check_Register_Inquiry form includes the CM_Transaction_Zoom window.

I thought the macros might actually reference the stored procedures that run to pull information, but I don't see them. In any case, I don't think the stored procedure is the problem.

I think your best bet would be to have someone take a closer look at the problem. I suggest creating a Dex SQL log of the error (steps are described here: support.microsoft.com/.../850996 ) and then opening a support case either directly with Microsoft or your partner.

You could post the log results to this thread, and possibly we can identify the problem without your use of a support case, but that's up to you.

Post back & let me know how you make out, I'm really curious!
Community Member Microsoft Employee on at

Like (0)

Report

RE: Bank Transaction Entry Zoom pulling up wrong check

I went ahead and pulled up the check via Checkbook Register Inquiry on a working machine, and a non-working PC. I ran a macro for both - here are the results for both (they are identical):

# DEXVERSION=11.00.0364.000 2 2
CheckActiveWin dictionary 'NBS Intercompany' form 'CM_Check_Register_Inquiry' window 'CM_Check_Register'
MoveTo field 'Zoom Button'
ClickHit field 'Zoom Button'
CheckFocusSpring line 2 browsewin 'CM_Check_Register_Inquiry_Scroll_Win'

NewActiveWin dictionary 'NBS Intercompany' form 'CM_Transaction_Zoom' window 'CM_Transaction_Zoom'
ActivateWindow dictionary 'NBS Intercompany' form 'CM_Transaction_Zoom' window 'CM_Transaction_Zoom'

Now, if I run a macro using Smartlist to view the check, it always works no matter what machine I'm on, and here is the macro code:

DEVELOPMENT SMARTLIST
# DEXVERSION=11.00.0364.000 2 2
CheckActiveWin dictionary 'SmartList' form 'ASI_Explorer' window 'ASI_Explorer'
MoveTo field 'ASI_ExplorerListView' item 0 # ''
DblClickHit field 'ASI_ExplorerListView' item 2 # '278716.00000'
NewActiveWin dictionary 'NBS Intercompany' form 'CM_Transaction_Zoom' window 'CM_Transaction_Zoom'
ActivateWindow dictionary 'NBS Intercompany' form 'CM_Transaction_Zoom' window 'CM_Transaction_Zoom'

Is there anything from this code that I should look into at more depth? Where do I access form 'CM_Check_Register_Inquiry' and window 'CM_Check_Register' to look at the differences bewtween the working and on-working system?

Also, I did run Checklinks on the entire Financial series and it came back with "no errors".
Lyn Barr on at

Like (0)

Report

RE: Bank Transaction Entry Zoom pulling up wrong check

Usually everything that happens when using a window is generated from various stored procedures. The easiest way to determine which stored procedures are running when doing various things is to record a macro & then to open the saved macro in Notepad.

If you're not sure how to do that, let me know.

You can also try running checklinks on the Financial series, under Microsoft Dynamics GP>>Maintenance>>Check Links. If it is bad data, that might help!
Community Member Microsoft Employee on at

Like (0)

Report

RE: Bank Transaction Entry Zoom pulling up wrong check

Hi Lyn. Thanks so much for replying. I didn't want to risk the Finance Director's GP install, so instead I took his GP2010 files and copied them over to the GP server. I expected the server GP instance to show the same issue the Director is having, but it still worked as it did before copying the files over (showed the proper check 2014 details). So we now know that it's likely not an issue with the installation files.

We also know, to the best of my knowledge, that it's not a bad link in the data because it does work:

A.) On the server (local install of GP - also houses the GP database)

B.) Finance Director's GP in SmartList

The issue only occurs on some of the Finance PC's. On our intern's computer, for example, it works just fine. On a few other Finance PC's, it doesn't work.

The main question I have now is, what happens in the background when you're in the Checkbook Register Inquiry window and then click on the "Number" link. I know it pulls up the Bank Transaction Entry Zoom window, but is that a stored procedure, or SQL view, or what?

By the way, I also checked the User Security section and the "windows" section for Bank Transaction Entry Zoom. SA and the Finance Director are set up the same, but we already know it's not a user security issue ... it's something on the PC. What could it be?
Lyn Barr on at

Like (0)

Report

RE: Bank Transaction Entry Zoom pulling up wrong check

I'm not surprised you have this issue, but I am surprised that it seems to be machine-specific. - It sounds like you tested on the "problem" machine as both a "regular" user and the 'sa' user, then tested again on the server as those same two users.

You could try copying the Program Files\Microsoft Dynamics\GP2010 folder from a working machine onto the non-working machine. That might resolve the problem.

I am more inclined to think that you have some bad links in your data, though, as a result of the duplicate check numbers. In other words, you may have this issue even after copying the program folder. Copying it shouldn't hurt, though, so it's worth trying. For added measure, you can rename the Finance Director's original folder first, as a backup.