How can I provide a partner user access to a report with order product fields?

Question

I have a report with Order and Order Product fields in it. The Partner Communities user has read permission to both Order and Order Product and no problem viewing them outside of reports (eg: in a detail page). The user can also access various other reports (all in the same folder). However, when a user tries to access the report, the message "Data Not Available" is displayed. Similarly, if user tries to create a new report based on the report type for that report then no order product fields are shown (but they are when an internal user accesses the same report type). I have changed the sharing for Order from "same as parent" to "private" and defined relevant sharing rules but still no go. Any suggestions?

I think that the problem may be rooted in the same issue described in this question.

Answer 1

Looks like there is a bug of sorts or undocumented limitation when it comes to accessing Order Products and a few other objects related to Product from custom report types. In this case, the workaround is to use the standard report type "Orders with Products" and you get access to Order Product fields.

Answer 2

The post you referenced would be out of date. Per Communities User Licenses at least read only access to all of the objects you mention, including Products, Pricebooks, Orders and Opportunities, is available to Partner Users provided you grant it to them.

There's a footnote on that page that may be worth noting to see if it applies to your org:

Once orders are enabled, standard profiles automatically include all object permissions for orders, as well as read access for products and price books. If your external users are assigned to a standard profile and these object permissions aren’t appropriate for them, consider creating custom profiles that don’t include these object permissions.

Although it sounds like you may have already read it, you may want to look at Received an "Insufficient Privileges" error message when trying to run a Report.

Edit

Here's an image of the schema that's involved taken from the SOAP API documentation at least a year or so ago, so it may be a bit out of date, but should still be fairly accurate. You can see the M-D relationships that exist which should propagate the record sharing and permissions that are necessary.