Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Issues Embedding Report in Salesforce

Objective: Embed PowerBI report in Salesforce   Issues: API Authentication/Stale token stored in Salesforce   Details:   I had followed the blog post on how embedding within Salesforce found he...
v-jiascu-msft's avatar
v-jiascu-msft
Microsoft Employee
8 years ago

Hi Anonymous,

 

Regarding to issue A:

1. The client info, like client id and client secret, is surely stable. So you can hard-code them. Did you get error message that the client info is invalid?

2. Did you upload all the things in the guide post?

Regarding to issue B:

Can you provide more info? Or I would suggest you open a support ticket here.

 

Best Regards,

Dale

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Background information: The report is located in a Premium capacity workspace and the hope is to distribute the report to the Sales team without needing to grant licenses.

 

Some additional information about the steps I took:

 

  1. Register App with Azure AD using onboarding tool: https://app.powerbi.com/embedsetup/userownsdata (This step wasn’t done as the service account, not sure of the implications of that)
  2. Grant permissions in AAD as Service Account (master account, admin of workspace)
  3. Create Salesforce Custom Setting OAuthApp_pbi
  4. Populate Custom Setting for PowerBI with AAD endpoints along with client id/secret
  5. Create OAuthController and PowerBIController Apex Classes with code from:  https://github.com/Microsoft/BusinessPlatformApps/tree/dev/Samples/Salesforce/EmbedPowerBIReport
  6. Add Azure AD to Salesforce’s Remote Site Settings
  7. Create Visualforce Page with code from GitHub repo linked above
  8. Add Report ID to Visualforce page code
  9. Navigate to Visualforce page located at:  OurSalesforceInstance.com/apex/PowerBI
  10. In pop up window, log in as the Service Account

 

 

Once all of these steps have been completed the iframe renders within Salesforce, but displays "This content is not available". Based on this blog post ( https://www.linkedin.com/pulse/success-power-bi-embedded-salesforce-fred-kaffenberger/ ) my next debugging step would be to use Fiddler to inspect the requests/replies. I'll work on that, but hopefully this additional information might point out where I went wrong.

 

Let me know if you have any ideas.

 

Thanks!