We are migrating a SSRS2017 Version 14.0.600.744 (October 2017) to PBIRS Version 1.6.7221.30698 (September 2019) via database update and almost everything goes fine, except the Report Parts. These kind of item are migrated also, but once in the PBIRS portal it does not show the item context menu by clicking on the three dots menu. Instead of shows the menu, it shows a message box saying:
Something went wrong. Please try again later.
Reviewing the RSPortal log file, we have found that PBIRS is trying to get the allowed actions that should be shown in the menu using a non existing API endpoint /Components(ItemId/Path=<ItemPath>)/AllowedActions:
Received request GET /api/v2.0/Components%28Path%3D%27/fec%27%29/AllowedActions| RequestID = s_2c25162f-9abc-4d48-a0c2-a207a372c40b
The same operation in SSRS2017 calls the proper API endpoint /Catalogitems(ItemId/Path=<ItemPath>)/AllowedActions:
Received request GET /api/v2.0/CatalogItems%28eb9bc5fc-c8f7-48e9-8e77-7ab4ed395a9d%29/Policies | RequestID = s_68a8e8f4-7254-453f-b98b-bac2554bef09
We have tried to create a new Report Part from scratch in PBIRS using Report Builder 15.0.1473.0 and the result is the same. The Report Part is saved into PBIRS and usable from Report Builder, but it does not show the item context menu. Even trying to upload the file using the portal, the behavior is the same.
This behavior in PBIRS seems by product design and is a bug under our eyes.
Can anybody give support on this? Anybody else has experienced the same?
Thanks in advance!