Management Reporter - Object not set to an instance of an object

(0) Share

Report

Posted on by Community Member

Customer is receiving this error in MR when attempting to move Building Blocks out of a folder and back out to the Report Definitions list. Has anyone seen this and fixed it? If you I'd really appreciate your help with this issue.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Suggested answer

Mahmoud Saadi 32,738 on at

Like (1)

Report
Copy link

Link copied!

Leslie has provided a check list to be considered when receiving this error, check it out on When things go wrong - 'Object reference not set to an instance of an object'

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks Mahmoud. I'd seen that article, and I've tried everything in it. Still getting error when I attempt to move building blocks out of a folder back to the root. I can move them from folder to folder, but I can't get them out of the folder to the root without getting the error and MR closing down.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

[quote user="DMLibby"]Customer is receiving this error in MR when attempting to move Building Blocks out of a folder and back out to the Report Definitions list. Has anyone seen this and fixed it? If you I'd really appreciate your help with this issue.[/quote]

I am getting that same error. Did you ever have luck resolving your issue?

Jessica

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

No unfortunately, I have not had any luck yet, in resolving this issue.

Was this reply helpful? Yes No
Suggested answer

Redbeard 12,931 on at

Like (0)

Report
Copy link

Link copied!

Have you tried exporting the Report components to a TDBX file, then deleting them and re-importing them into the right location(s)?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks Harry. No I haven't tried that. But I definitely can. Also wondering why this is happening to begin with. But maybe just one of those strange happenings that no one can explain.

Was this reply helpful? Yes No
Suggested answer

Kristie McNulty 1,008 on at

Like (0)

Report
Copy link

Link copied!

We found that not all of our segment names for the segments used in the chart of accounts were the same in every company. One company had NATURAL while all of the other companies had Natural for the third segment in our COA. Once we renamed the uppercase to mixed case, Management Reporter worked for all companies. Our version is 2.12.15000.56. Case does matter for your COA's segment names.

Was this reply helpful? Yes No
Suggested answer

Lisa at AonC.com 1,137 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

One of our GP 2016 (16.00.0439)/MR 2.12.15000.56 clients ran into this non-descript error after reversing the GL year-end close. They did have differences in the case of their segments (some companies had a segment named ACCOUNT and others had it as Account.) After reviewing/standardizing the account formats (company table SY00300 and Account Format GP window) and rebuilding the Data Mart, the problem persisted. I then copied/pasted the row details to a new row. The new row worked (with no changes).

Reversing the GL year-end close was due to new GL accounts not being set with the proper Posting Type. (The new accounts were Profit & Loss and the problem report was a balance sheet so there was no change to the row due to the new accounts.)

Therefore, I can't tell if the source of the problem was reversing the close or the segment names. (I did not have to rebuild the data mart again after recreating the row.)

Was this reply helpful? Yes No