2 Replies Latest reply on Mar 10, 2020 11:30 AM by Elliott Stam

    Possible bug: 'delete extracts of embedded data sources from a workbook' endpoint errors if multiple extracts present

    Elliott Stam

      Hey there,

       

      This one's for the REST API dev team: the 'delete extracts of embedded data sources from a workbook' endpoint, which converts embedded extracts into live connections, may have a bug.

       

      When I run it on a workbook that has two embedded connections (to the same database, with passwords embedded in the workbook), I get the error shown at the bottom of this post. However, every time it happens, one of the datasources in the workbook is converted to the live connection. So here's the pattern:

       

      1) publish a dashboard and make sure it has two embedded data source connections (with embedded passwords)

      2) run the 'delete extracts of embedded data sources from a workbook' API call on the workbook

      3) get the error posted below

      4) confirm that one of the embedded datasources is now a live connection, but the other is still an extract

      5) run the 'delete extracts of embedded data sources from a workbook API call on the workbook (again)

      6) receive no error (instead we get a successful 200 status code)

      7) verify that both embedded connections are now live rather than extracts

       

      The error received when the workbook has more than one embedded extract:

      {"error":{"summary":"Bad Request","detail":"There was a problem deleting extract for workbook \'c8c58e90-8a56-4183-a3f6-417706638eae\'.","code":"409080"}}

       

      Thanks,

      Elliott