Skip to content

Commit 14216be

Browse files
committed
note reorder
1 parent c04b4ed commit 14216be

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-machines/workloads/sap/expose-sap-odata-to-power-query.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -162,11 +162,11 @@ The described approach is also applicable to write-back scenarios. For example,
162162

163163
:::image type="content" source="media/expose-sap-odata-to-power-query/powerbi-flow-enabled-dashboard.png" alt-text="Screenshot that shows the flow-enabled Power BI service dashboard.":::
164164

165+
The highlighted button triggers a flow that forwards the OData PATCH request to the SAP Gateway to change the business partner role.
166+
165167
> [!NOTE]
166168
> Use the Azure API Management [policy for SAP](https://github.com/Azure/api-management-policy-snippets/blob/master/examples/Request%20OAuth2%20access%20token%20from%20SAP%20using%20AAD%20JWT%20token.xml) to handle the authentication and CSRF token outside of the flow.
167169
168-
The highlighted button triggers a flow that forwards the OData PATCH request to the SAP Gateway to change the business partner role.
169-
170170
:::image type="content" source="media/expose-sap-odata-to-power-query/power-automate-powerbi-button-flow.png" alt-text="Screenshot that shows the flow on Power Automate requesting the business partner change on the SAP back end.":::
171171

172172
## Next steps

0 commit comments

Comments
 (0)