Regarding the range, etc, it's really not going to be too troublesome, mate.
Basically all you'd do is:
- Identify incoming data
(as agnostically as possible - ie. not prescriptively looking for specific things)
- Use a Select to build an object for each row
- Place that as the value for the 'values' key in the excel call
- Send the call
With any luck there's no formatting and/or formulas needed, but that needn't be a big deal, either.
I'll demo with some of @rpinxt's data if they give us something nice to work with ... but you're brainier than me, so I'm sure you'll get it. It's just logic stuff, really.
Like I say, though, what's key is to annotate everything, here. I would suggest (to rpinxt) that it all be in a separate Compose or two in key areas, for future users of the flow.
Also, since it might have complexities, it should maybe have some very basic error handling, but that's super simple.
----
There are a LOT of functions available in the excel Graph stuff, many of which aren't in Flow as actions.
For example, if you wanted to get the entire used area of a worksheet then there's the getusedrange Graph call (which I've mentioned before but can't remember if you were in thread) which works whether or not a table is there at all.
I've used that to get data when there's no table around, or (if desired) to find the area of which to make one.
Obviously I'm not saying that as a specifically useful thing here, necessarily, just that there's a lot that can be done. I'm very confident that I'll have this pushing the data across without too much hassle. But it will still be a lot to process, and should be handled properly (ie. using Select/Filter/etc.) to ensure that it's managed correctly.
----
Oh, and hehehehe ... I know how you feel about touching some of these actions, I do it all the time ... like ... I *constantly* forget how useful the OneDrive Convert action is, or that it exists.
Also ... just like the SharePoint API call, it occasionally gets fussy about HTTP encoding when there's more than one or two GUIDs in there.
----
Finally ... I'd really like to offer a HUGE piece of advice here, over and above everything that's being discussed ... and it really and truly is stated without any 'poking' at anything:
Reports and Excel, in general, are not the best way way to display data anymore.
There's far better ways to impart the information which mean that none of this need ever be done.
By far the easiest of these is bespoke SharePoint pages and/or list views, which can ALWAYS be up to date information which shows exactly what the person viewing it needs to see. These can be tailored to groups, public, private, individual, etc, and even be tabs on Teams channels.
If you need an excel sheet for some legacy system to process it, that's understandable, however producing a report should rarely (if ever) be required for anything other than one-off occasions.
However, if I *am* automating something, or placing it in a more responsive format (like SharePoint) then I'll always build in a 'I don't like it' button for people that refuse to move from legacy ways of doing things.
This means that they can still have their cake, and you can eat it. 😉