One of the best parts which we check above is Relationships are correctly shown as it is in CDS

• 2nd is adding lookup, Options field, regarding field all will give Name /Label and values both as separate Fields , for which we need to do some extra work when getting data from Odata.
• Below I have selected Lookup and Options fields as Name and ID

• We will use the above report itself to embed in Microsoft dynamics 365
• We have added only account and contact entity with some field to demonstrate how Relationship are pre-build and we get Lookup name and Id
• Now we will publish the report, select the workplace

• Once published, we will edit credentials as OAuth
• Navigate to My Workspace -> DataSets and edit credentials

• Selecting Authentication Method as “OAUTH”
• Remember to enable Below.
  End users use their own OAuth2 credentials when accessing this data source via DirectQuery.

• Now we will ping Report as live so it can be used in dynamics 365
• Navigating to report from workspace

• Once pinned, we can see a pinned item in DashBoard, and will also be available as a dashboard in D365
• I have changed name while pinning it as a dashboard

• Navigating to D365 Dashboard
• Clicking NEW, Either select Microsoft dynamics 365 or Power Bi Dashboard.
• Select Layout

• Select Power BI Tile
• All our Dashboard in Selected workspace will be available

In the previous post, we enabled TDS Endpoint using a utility  Microsoft.Crm.SE.OrgDBOrgSettingsTool .  But now we have an option to enable the TDS endpoint from http://admin.powerplatform.microsoft.com/ .

• Navigate to http://admin.powerplatform.microsoft.com/ -> Select Environment -> In Features, we will find en checkbox for enabling the TDS endpoint. That will make a connection to the SQL server possible.
• Also, enable Power Bi Visualization embedding
• Verify that your environment has at least version 9.1.0.17437.

Once Prerequisites are completed we are ready to Get data using SQL Server

• Click on Get Data -> select SQL Server and enter Details
  i.e ORGNAME.crm.dynamics.com,5558 (replace CRM as regions ) , Optional Database (ORGNAME)
• Select DirectQuery as an option and Click OK

• Now we will do authentication using Microsoft account and connect

• After Successful connection, let us select some entities and select load

• I would be selecting Account and Contact and Load

• previously when we use to get data using Odata, we needed to transform data instead of load, we can still transform data but it has reduced a lot of work after getting entities we will see that next

Once the connection is created, In the model we will see relationship connection pre-created. we don’t have to do much work regarding relationships.

As previously we use to create relationship again in Power BI.

One of the best parts which we check above is Relationships are correctly shown as it is in CDS

• 2nd is adding lookup, Options field, regarding field all will give Name /Label and values both as separate Fields, for which we need to do some extra work when getting data from Odata.
• Below I have selected Lookup and Options fields as Name and ID

But Not all org Connect successfully, we need to attend some prerequisites. i.e Download the OrgDBOrgSettingsTool and configure Microsoft.Crm.SE.OrgDBOrgSettingsTool.exe.config file.

——————————
ADDITIONAL INFORMATION:

Login failed: TDS protocol endpoint is disabled for this organization. For more information, please visit http://aka.ms/EnableSQLForCDS
RequestId: TDS;6d3b31e8-d260-410c-9a23-cca78cbd1795;2
Time: 2020-05-21T07:17:56.0358439Z (Microsoft SQL Server, Error: 18456)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476

Follow instruction from here: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/view-entity-data-power-bi

1. Sign into Power Apps, and then select the appropriate environment from the top-right corner.
2. Verify that your enviroment has version 9.1.0.17437. To do this, select the Settings gear on the toolbar, and then select Advanced Settings. Then, on the new browser tab that opens select the Settings gear on the toolbar, and then select About.
3. Download the OrgDBOrgSettingsTool. During the download, select CRM2016-Tools-KB4046795-ENU-amd64.exe. After the download is completed, install the tool.
4. Open the Microsoft.Crm.SE.OrgDBOrgSettingsTool.exe.config file and make the following changes. For example, if your advanced settings environment URL is https://orgbb33fb45f.crm3.dynamics.com/main.aspx the OrgDBOrgSettingsTool_CrmDiscoveryService_CrmDiscoveryService value will be https://disco.crm3.dynamics.com/XRMServices/2011/Discovery.svc and the OrgDBOrgSettingsTool_OrgServiceUri value will be https://orgbb33fb45f.crm3.dynamics.com/XrmServices/2011/Organization.svc.

5. Add the following node within the <configuration> node in the Microsoft.Crm.SE.OrgDBOrgSettingsTool.exe.config file:

  <runtime>
      <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSchUseStrongCrypto=false"/>
  </runtime>

6. Open a command window, move to the folder where the OrgDBOrgSettingsTool contents are located, and run the following command:

• • Microsoft.Crm.SE.OrgDBOrgSettingsTool Update /u <org-unique-name> EnableTDSEndpoint true
  • Replacing <org-unique-name> with Org unique name

Reference : https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/cds-sql-query