@v-lin-msft
So when I built the flow, I built it using a Static Workbook. Once the Flow was confirmed working, I changed the Values from Static to Dynamic based on each workbook within a library.
Now what I don't get, is that I have a very similar Flow already built and, has been working for months. The only difference being the Workbooks are referenced in OneDrive for Business. At present, I have to copy each Workbook from SharePoint to a OneDrive for Business Location then, do the extract.
Considering OneDrive for Business is just a Personal SharePoint Site, I can't see why there is a difference in this. I need to export the SharePoint Flow to provide as a solution to others and, making it jump to a Folder on somebody's Personal OneDrive for Business is not an option.
In addtion, the OneDrive Flow is extracting the data to CDS however, I have now been told that my A5 Licence which includes PowerApps does not include the feature of using the Model Entity which, seems to be pointless on the basis that the new Data Flows are all designed to use CDS.
Using the Canavas App is too time consuming for the level of relationships within the data in respect of designing Forms and Views let alone the Layout's of these. I could possibly accept having to use the Canvas App if Data flows had the ability to extract data from more than one Excel Workbook at a time.
MS Flow has so much potential but, the 3rd Party Connectors seem to be the only reliable ones. Microsoft Flow Connectors have features that seem to be removed on a constant basis. There is a Road Map for everything but, I don't see a Road Map for Microsoft Connectors and, when they are updated, the feautres that have either been added or depreciated.
