Merged PR 18451: fix setAccessToken bug

When embed type was create, visual or qna the setAccessToken did not do anything

Author: somriar

dist/powerbi-client.d.ts

@@ -1,4 +1,4 @@
-/*! powerbi-client v2.7.0 | (c) 2016 Microsoft Corporation MIT */
+/*! powerbi-client v2.7.1 | (c) 2016 Microsoft Corporation MIT */
 declare module "util" {
     /**
      * Raises a custom event with event data on the specified HTML element.

dist/powerbi.js

@@ -1,6 +1,6 @@
 {
   "name": "powerbi-client",
-  "version": "2.7.0",
+  "version": "2.7.1",
   "description": "JavaScript library for embedding Power BI into your apps. Provides service which makes it easy to embed different types of components and an object model which allows easy interaction with these components such as changing pages, applying filters, and responding to data selection.",
   "main": "dist/powerbi.js",
   "typings": "dist/powerbi-client.d.ts",

dist/powerbi.min.js

@@ -1,5 +1,5 @@
 const config = {
-  version: '2.7.0',
+  version: '2.7.1',
   type: 'js'
 };
 

package.json

@@ -383,6 +383,7 @@ export abstract class Embed {
    */
   setAccessToken(accessToken: string): Promise<void> {
     var embedType = this.config.type;
+    embedType = (embedType === 'create' || embedType === 'visual' || embedType === 'qna') ? 'report' : embedType;
     return this.service.hpm.post<models.IError[]>('/' + embedType + '/token', accessToken, { uid: this.config.uniqueId }, this.iframe.contentWindow)
       .then(response => {
         this.config.accessToken = accessToken;