Forum Discussion
AdministratorUnable to add Dataverse for Teams as source in DataFlows
AdministratorHey @Sebastian030 ,
>> The workaround that you've posted on 02-28-2022 04:52 PM shows a way to create a new cloud-flow, not a data flow or am i wrong?
You're not wrong. I needed a cloud flow to store some data from DataVerse for Teams also in an on-prem SQL Server.
The 'Dataflows (Preview)' tab wasn't there yet when I posted this, but it's a welcome addition.
>> That still doesn't solve my problem to access the tables/data from an existing dataflow in "Dataverse for Teams" with a new dataflow within the same Team.
Interesting, just tried that myself but also don't have the possibility to access tables/data that way from DataVerse for Teams.
>> Did you manage to realize that with your provided solution?
No, my case was to extract source data from an on-prem SQL Server and inject that in DataVerse tables for use in a Power App.
Grtz,
KrAck
>> That still doesn't solve my problem to access the tables/data from an existing dataflow in "Dataverse for Teams" with a new dataflow within the same Team.
AdministratorHey @KrAck thank you for your reply.
I found a solution to use the tables from Dataflow1 as source for Dataflow2.
@ujjS_9 this might work for your too.
Situation is:
- Dataverse for Teams
- Dataflow1 creates two tables (or less/more)
- Dataflow2 should use tables/data from Dataflow1 as source
The Microsoft Documentation showed a possible solution using OData.Feed
Here's how i managed to get it work:
1. Get the Instance URL for the Environments by
1.1 clicking the "Info" tab in Power Apps for Teams
1.2 clicking "Session Details"
1.3 Get the value of "Instance url" i.e. https://
1.4 modify the url by adding "/api/data/v9.2/"
to get the final url (https://
2. Follow the above linked microsoft documentation to access the dataverse using OData.Feed
2.1 I had some issues with the authentication and my organisational account. When i pressed the "Sign in" button in Power Apps for Teams, edge would open a new tab and close it immediately. I found a workaound by opening Power Apps for Teams in PowerApps using the three dots (...) next to your Team Name in Power Apps for Teams.
This workaround definately feels wrong, but so far its the only solution ive found.
If anyone found a different solution please let me know.
Greetings