Hi Jeff and Kayla,
Here is the detail of the issue from Connect, which explains why it's happening. Notice in this description that I suggest how to work around it as well.
It would appear that the Account Transactions SmartList was edited in GP 2013 such that Account Number is now pulled based on Account Index. Because the account index is numbered in the order that the accounts are added as opposed to the logical order of the accounts, this is creating undesired results when using the "between", "greater than" and "less than" booleans.
Here is an example:
This is a truncated list of an account range from the GL account master table:
ACTINDX ACTNUMBR_1 ACTNUMBR_2 MNACSGMT
436 1270 015 1270
438 1271 015 1271
439 1272 015 1272
19 1275 015 1275
20 1276 015 1276
21 1277 015 1277
437 1278 015 1278
22 1279 015 1279
Notice, for example, that the account index for account 1278 is not between the account index for account numbers 1275, 1276, 1277 & 1279 because it was added after the initial setup. When you qualify the Account Transactions SmartList by the range of 1275 – 1279, while it does return data, it doesn’t return any data for account 1278 even though there is data in this account. It appears that this is because it is actually looking for the range between 19 & 22, and 437 is not in this range. When you qualify the same SmartList by 1270 – 1279, it appears to think that the beginning of the range is 436 and the end is 22. Since the beginning is after the end, it returns nothing. However, all accounts in the range actually contain data. This is just one example, but I've done fairly extensive testing of the logic that I describe here, and it holds true every time.
It is possible to produce correct results by using Account or Main Account Segment as the qualifier instead of Account Number. However, because Account Number is the column that shows in this SmartList by default, it is the one that users are normally selecting. Users are getting erroneous data, and aren't necessarily even realizing it.
Microsoft closed the with the following comment: "Thank you for your posting, your issue looks to be a support issue and not a suggestion. Please contact your partner or Microsoft support for additional help on this issue. Best regards."
Of course, I am the partner and I'm certain that they are incorrect, but I was extremely busy at the time and didn't have time to push back. I can still click through to the link, and can see that three other people have indicated that they're having the same issue. I'm actually surprised there aren't more. I have seen a few cases where partners have rebutted and either requested that the case be reopened or simply started a new one, but I have not done that to date. My client is still experiencing this issue, but is using the work-around noted above.
The client is using the Historical Journal Entry Lookup window under the Inquiry menu in order to work around item #1 in my original post.
Hopefully this helps!
Kimberley
