Insert row can not be used with file ID. Get rows and other actions work fine.
Also, when EXCEL file is replaced,ID changes and flow don't recognise it anymore. The idea would
be to make ID dynamic , not static.
Thank you for the suggestion. What you are asking for is the ability to use an action with dynamic input but without selecting a particular file when you're designing the flow. We will evaluate this feature.
You also can't create a table in an excel file and then add data to that new table.
So I am thinking on a trigger initiated by a user from a Sharepoint Document Library for a selected file, in my case an Excel file. The next step I would like to achieve is to List rows present in a table, assuming all files stored in the Sharepoint Library are excel files with the same table structures.
The scenario is detailed in moredetail here: https://powerusers.microsoft.com/t5/Building-Flows/Excel-Business-problems/m-p/107609
According to Microsoft's Flow team response; Microsoft flow support to select a file from the picker in the "Excel (Business)" connector currently, but choosing a dynamic content in the "File" field to select a file is not supported in Microsoft flow "Excel (Business)" connector currently.
Although the inputs on both action "List rows present in a table" blocks are apparently the same,the inputs on select a file from the picker is a friendly format of the file identifier,you couldn't choose a dynamic content in the "File" field to select a file.
So If I want to choose a dynamic content in the "File" field to select a file, there is no way to achieve it in Microsoft Flow currently.
As suggested, I am submitting an idea to Flow Ideas Forum.
I would like to second this request. It would be very useful to dynamically assign an excel online file. Currently, I'm writing to a template file which is then copied to a designated folder. This works unless multiple flows are running, and then you run the risk of copying over the template file while another flow is in use. I've designed it to wait until the excel file is not in use, but simply being able to dynamically assign a file would greatly reduce the complexity and increase the flows efficiency.
I currently need this connector too. I'm using OneDrive as a workaround, but it's no ideal.
I also need this. Having to select a single workbook rather than dynamically select one really limits the usefulness of this connector.
It's a +1 from me!
I have some export scenarios where this would be extremely useful; right now I'm forced down the same road as Streamer is, working using a template file, but it's far from ideal and appalling from a performance point of view!
Dynamic file names need to be supported, should be easy to add this feature.
For me this is plus 2 if possible. It is quite strange that it is not possible to dynamically pick file in excel for business as we are able to define flow to start manually for items in SharePoint document library...
Even weirder is that dynamic file names works fine with the OneDrive "Get file content using path"
This is sorely needed. No reason why I shouldn't be able to use a variable to specify the file name.
In my case I'm converting multiple files from Smartsheet (using the Smartsheet API) into Excel, and then trying to format them as a table with the Excel "Create Table" API.
Since I can't specify the filename dynamically and MUST choose it from the dropdown, I can't use dynamic file names. While in my case it would always be the same 4 files, issue here is with the OneDrive for Business sharing locks that often (even though noone else other than the Flow accesses the files) sometimes keeps the files locked for an extended period of time, and then I can't overwrite them. (another issue entirely)But having the ability to dynamically specify the filename for any of the Excel APIs (whether on SharePoint, OneDrive for Business, or regular OneDrive) would be VERY VERY VERY useful. In this case, I could revert to my prior method of creating a unique file name based on date and time (which I'd prefer anyway).
Please fix this! 🙂