FR #value errors in Excel 64bit

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.

Parents
  • 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

Reply
  • 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

Children