PBIRS January 2020 : API Issue ?

[vivien57]

Good morning all,

I just went to the PBIRS version January 2020 and I have a problem (before I was in May 2019 version)

Before I used this feature to have dynamic images in my dashboard : 

https://server/Reports/api/v2.0/CatalogItems(Path='/images/circle-delete.png')/Content/$value

Now it doesn't work anymore, the erros is :

{
  "error":{
    "code":"","message":"No HTTP resource was found that matches the request URI 'http://server/Reports/api/v2.0/CatalogItems(Path='/images/circle-delete.png')/Content/$value'."
  }
} 

Have you encountered this problem ? 

Thank in advance,

Vivien

[Jon-Heide]

Try getting the item by ID rather than path. You can see info at: https://app.swaggerhub.com/apis/microsoft-rs/PBIRS/2.0#/CatalogItems/GetCatalogItemContent.

[vivien57]

Hello, 

Thanks for your feedback. 

The problem is : the ID is different because it depends on the environment (DEV, UAT, PROD). While the path is generic.

Moreover, it worked with the May 2019 version and i didn't red that it was depreciated feature (in January 2020 version).

Thank in advance for your return,

Vivien

[d_gosbell]

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. GUID example: 01234567-89ab-cdef-0123-456789abcdef path example: path='/folder1/folder2/item' If the path itself contains single quote, it should be escaped - add another single quote.

And if you make the call without the /Content/$value you do get back a valid json payload when using the path= syntax.

[vivien57]

Good morning all,

Via the opening of a ticket at Microsoft, they confirm that it is a bug. They are working on it.

[Anonymous]

Will you update here if you get any estimated release date etc.? I have the same issue and it is quite a problem.

[vivien57]

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:

               http://servername/reports_pbi/api/v2.0/Resources(5ffc40b7-e773-4027-98df-cb6c92d60ddf)/Content/$valu...