Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I have a client who uses the historical stock status report, and after the 2019 year-end update to GP version 18.2.1036, the report doesn't total correctly. Here are some screenshots:
Here's what the report used to look like on their version 18.00.0704 (they have a test environment and we were able to test it:
Here's what it looks like now: Every item is subtotaling.
I believe this is a bug - I know most clients don't use this report, but this one client does. I have confirmed the report settings are the same between the two environments, and neither is using a custom report format.
Do you have page 1 of the prior report? Comparing the headings is very useful for these types of questions/issues.
I also strongly encourage moving to the Historical Inventory Trial Balance if it is an option. It has been the recommend report for many versions and has much better information for tying to the general ledger. :)
I do have page 1 of the pre-upgrade report. Here it is:
I think to make that move, we'll probably have to do an HITB reset - the current HITB is $1.6MM different, and so the Historical Stock Status was more in line with the figures they knew as accurate. As far as I know, there's no real way to adjust the HITB report without a reset...is there?
Thank you for the screenshot! They report options definitely look the same. Since you have both versions available, can you compare the reports in Report Writer and Table Resources? I'm thinking there may be a new sort added to one of the tables (for performance reasons) but I'm not seeing anything in documentation to support that. (This is where having a current SDK would be so helpful.) Hopefully you can identify a difference in a header/footer sort that you can correct with modifying the report.Regarding HITB, you are correct that it requires a reset. (GP takes inventory subsidiary and GL accounts down to $0 and then brings back in all the data. This is a critical step to keep the two in balance with the new data table/reporting.) Once you are through the upgrade issues, I recommend using that test environment, or even a test company in the production environment to test out the HITB reset/report.
I did compare the two reports, and at the table and sorting levels, I see no difference. In fact, there are no sort options at the table level. The section options between the two reports matched as well. I did see some changes in the upgraded report where the visibility was turned off for some fields in the item footer. Just to make sure, I created a custom report on the non-upgraded test machine - I made no changes, just opened the report in report writer. I then moved this report into the reports.dic for the upgraded server by copying the reports.dic from the old machine and then importing that one report into the reports.dic of the upgraded server. I still got the same result. Whatever was changed appears to have been changed at a code level that I can't see.
How about trying the report from TWO (Fabrikam) sample company? I get the data subtotaled by account when I run it from there (18.2.1036). For example:I'm thinking it may have something to do with your Sort Order on the Account Format. Do you really have only one segment in your account? Is the Sort set to that account? (I can't tell if you have a segment named "Account Number" or if you have a one-segment account.) Check Links on the Account Master will update the Main Segment based on that sort.
They really do only have one GL account segment. There is no sort order specified - could that be the problem?
I did run the report on Fabrikam on their server, and I'm getting the same kind of funky results there as well.
Just to confirm, I also tested this on my own local test instance for the same version. My results matched yours - not the client's.
And, to make matters even stranger, I installed the GP 2018 HITB reset tool, and when I try to run it, I get this error when launching it through GP:
(I think I'll start a second thread on this one after seeing if I can find the answer through some searches.
The blank Sorting Options is to be expected with a single account segment. (It dates back to a frustrating decision made around version 3.0 to not allow a sort on the first segment in the Account Framework.)
If you have access to a test company on the client's server, add a second segment to the account framework and see if (1) there is a sort defined in Account Framework for the second segment and (2) if the HSS report stops subtotaling after every item.
[I'm not familiar with the HITB error. I'd run Grant.SQL and make sure to launch GP with Run as Administrator and log in as sa to troubleshoot. If that doesn't clear it, a SQL trace or debugger may provide more clues.]
Sadly, adding another segment didn't fix the report. I don't have the issue on my local machine, so it has to be something with their environment (but even the Fabrikam database is producing the faulty report, so I'm not so sure it's data related.) It just didn't happen prior to the year-end update.
At this point, they've decided they'd rather use the HITB reset tool and get that back in line. So now I'm focused on trying to fix that :-( I did run the Grant.SQL, and ran GP as Administrator. I captured an SQL profile, but I don't see the error in the profile.
They will really like HITB! And if you like SQL, you will LOVE the SEE30303 table.
Regarding the Reset error, I would look into the Account Framework tables to see if there is something amiss there.
[Did you try the HITB Reset tool on your working environment? Perhaps it is not compatible with 18.2 yet.]
I did try this on my working enviornment as well, and I'm betting you're right - it's not compatible yet. I hope they hurry up! ;-)
So, the issue with the HITB reset tool was a break in the last build. Microsoft sent over a new .cnk file, and so I was able to reset it. But now, I have the same subtotaling issue with the HITB, where it's inserting a subtotal by account between each item. So, I don't know what choice I have but to open a case with Microsoft to get to the bottom of this....it's weird it was one report, but now it's two reports.
Strange. It sounds like you have definitely isolated it as an environment issue. It seems like there is something with the System-Level Account Framework, perhaps related to it being a single segment. Microsoft would be the best resource.
Hey there -
First, thank you for all of the time you spent corresponding with me on this issue. I wanted to follow up because we opened a case with Microsoft.
For some reason, the year-end update corrupted something in the installation of GP2018. We found this out by renaming the GP2018 program files folder, then repairing Dynamics GP. Once we did that, the reports started totaling correctly again. We then added in the 3rd party product, testing the report each time, and the issue didn't come back. So, as far as a fix, the answer is to rename the folder in C:\Program Files(x86)\Microsoft Dyamics\GP\ to something other than "GP", then go into Add and Remove Programs and repair Dynamics GP.
Business Applications communities