Skip to content

x Want to ask a question or reply? Click here to join the group.
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 103 subscribers
  • Views 1328 views
  • Users 0 members are here
Browse Forums
Announcements
388
topics
261
replies
Databases and Operating Systems
606
topics
2k
replies
Financials Suite
738
topics
2k
replies
General Discussion
2k
topics
9k
replies
Operational Suite
459
topics
1k
replies
Reporting and Analytics
480
topics
1k
replies
Reports, Macros, Customizations and Developers
605
topics
2k
replies
Sage CRM for Sage 300
101
topics
268
replies

FR #value errors in Excel 64bit

Michael Seemann
Solved
Posted By

Hi Sage Community!

Old machine, Excel and Office 32 bit. Run report, no issues. New machine, MS 365 64 bit run exact same report and get #value errors in every calculated field. The formula is simple column D minus column C. Suppress zeros also fails. Report executes without errors, except the result is filled with #value errors. Again, same report works in 32 bit. Same result if I "design" or "run" the report.

Is this a subtle setting in Excel that didn't transfer over? A rogue add-in. I was under the impression that Excel 64 bit now works with Financial Reporter.

What am I missing here?

Michael

Details:

New machine: Window11, Office 365 64 bit, Sage 300 ERP 2024 PU3.

Old machine: Windows 10. Office 2016 32 bit, Sage 300 ERP 2024 PU3.

  • 0

    Check with Sage Support as 2024 FR related hot fix were released.

  • 0 in reply to krishneil

    Thank you, Krishneil, for your prompt and awesome reply. I did locate the hotfix .dll file. This solved half the problem. The suppress zero issue is solved but unfortunately the #Value errors persist. I did not locate another hotfix to address this.

    As mentioned, the formulas are  just working on variances between years (numbers that FR is pulling correctly). The simple E5-C5 calculation returns #value.

    The date on the hotfix is pretty recent. Is it possible that Sage does not know about this issue and that this is a new bug?

    Any additional help here is much appreciated.

    Michael

  • 0 in reply to Michael Seemann

    Did you reach out to sage support or your business partner to  raise with sage support team for a resolution.

  • 0 in reply to krishneil

    I reached out to Sage directly to avoid the VAR getting in the middle. No resolution yet. I was asked to upgrade from 2024 PU3 to 2024 PU8 but that is a lot of work when there is no guarantee that this will actually work. As far as I know there is no documented issue with this that the upgrade will fix for sure. The previous hotfix was a single DLL file. I am thinking that I should be able to get a single DLL file to fix this. If 2024 is a supported version, upgrading should not be necessary at this time.

  • +1
    Verified Answer

    After reaching out to Sage Technical Support, it was deemed to be a bug, but also a bug that had no fix in 2024. It was suggested that we update to 2025 or later. Since we have a few 3rd party software modules, these upgrades are not always easy to do. We picked Spring Break and between finance and IT, we performed an update/upgrade to 2026 PU1. This issue/bug as resolved itself as a result of the update. If something else raises its head, I will reopen the case with Sage. As of right now, the issue is solved.

*Community Hub is the new name for Sage City