Forum Discussion
PBIRS January 2020 : API Issue ?
This does sound like a bug, I just checked on a Sep 2019 instance and the path= format works there too, but not on a Jan 2020 instance.
Jon-Heide the documentation you linked to has the following note about the Id for this call so I think it should be supported:
|
Id *
string($string)
(path)
|
The key (GUID or path) that uniquely identifies the object. |
And if you make the call without the /Content/$value you do get back a valid json payload when using the path= syntax.
Good morning all,
Via the opening of a ticket at Microsoft, they confirm that it is a bug. They are working on it.
Will you update here if you get any estimated release date etc.? I have the same issue and it is quite a problem.No, I don't think there will be an update to correct the problem.
I think this will be fixed in the next version.The current workaround is as follows :
You can use the following APIs to get the Id of the item:
http://servername/reports_pbi/api/v2.0/Resources(Path='/image.jpg')?$select=id
This will return the following output:
{
"@odata.context":"http://infinity-pc/reports_pbi/api/v2.0/$metadata#Resources(Id)/$entity","Id":"5ffc40b7-e773-4027-98df-cb6c92d60ddf"
}
You can then use the Id to for the API call to display the content: