there are several Revit to Excel link apps/programs but none that I know of that automate the process like you want. Generally it's export the data from Revit, import the data into Excel, modify the data in Excel, send it back to Revit. You might post in the Dynamo forum with the question. I don't do Dynamo but there are some pretty cool things that it can do.

Why not monitor the data with a Revit schedule?

....I don't do Dynamo but there are some pretty cool things that it can do....

You can teach an old dog new tricks

If i will use schedules, it needs updating every time. and same for dynamo, we need to link it again and again. And let's assume if i need to see the data after every 2 mins, that will be really time consuming to create schedule in each section or links using dynamo.

Huh?
Sorry, but that's just wrong.
Schedules in Revit are live and update immediately with ANY change. WE use them that way all the time.
Are you sure you're not thinking of ArchiCAD?

...or the spanner lisp? Bwahaha

I am presuming Billy wants to do what I've always wanted to do - that is

"Get into the backend of the .rvt format in order to link directly, live, to an alternative reporting platform"

i.e. Excel, Access, PowerBI, Tableau, etc....

So yes, whilst Schedules are "live", in Revit, the truth remains schedules (in Revit) are limited, offering little to those who want to "drill" around a dataset - essentially forcing the (Revit) user to define multitudes of schedules (with each adding significant calculation load) if they want "overview",

We're up against this at the very moment on an exercise where we are working up a massing study with 6 options. Scheduling Masses, Mass Floors & Areas for all 6 variants, for reporting (on sheets), controlling (in model edits) and exporting (more on that in a moment), mean we have at least 54 schedules - just for masses.

What we are presently doing is taking 18 of those schedules, (masses, mass floors & areas x 6) and linking them into Access, using a union query across all 18 to produce a single .csv, then reviewing and reporting the data (all at once) in an Excel Pivot. Whilst playing with the same .csv connected PowerBI at the same time.

Since "live" connections aren't an option*, and batch exporting schedules still absent OOTB, it's the actual "push" (out) that's a manual bore - and breaks the immediacy of the data review - whereas the rest of the steps amount to less than 10 clicks (open Access, open file, refresh data, export .csv, open Excel, open file, refresh data, print).

*RevitDBLink seemed to promise a bettery way, but it stalls HARD on large models - so (in my experience) works only as daily-data-dump (run out of hours) - but then I only ever got my head around connecting to .accdb, as I never quite understood the setup of the ODBC connection the addin. also provides.

I did once read about the possibility of connecting Revit Server-hosted models to platfroms like PowerBI using the POST protocol, but that to is a bit too higher-learning for my little brain.

Then yes, there is Dynamo, or perhaps even better for "live" links, Flux, but the "issue" (as I see it) is that both appear to need some direction - i.e. in Flux, you set up "keys" - but setting up a "key" for every parameter value you might ever want to "drill", given the vast number of Revit parameters & propertoes, would essentially be like 1:1 mapping every concievable value - and I can't imagine that'd perform nicely. Likewise, Dynamo would still operate on a "what is it you want to look at", whilst also not truly being a "live" port of the data.

Yaah u got my point. What do u think about building an add-in to automate the process? From taking data to showing it in excel.....

Trust me, if I had the smarts I'd have it done already, flogged it and be basking in the sun someplace!

But the way the world is working right now with "bake your own" approaches - means even if I had the time and funding, I wouldn't be aiming at Excel as a "final goal" anyway, but "just" the connector. Crystal ball suggests progress would hit a brick wall and would all trickle back into A'desk's lap to have them open up the API more - exposing the data parts folks like you and me seem so keen to get our grubby mits on.

But as it is I'm busy these days, still noting all the differences (and potential) of the format/outputs we can get;
the accessible (and locked out) parameters in Revit,
the additional (often very useful) properties exposed once in Navisworks (IsFlipped, etc),
the tables exposed by RevitDBLink (RoomAssociations for one)
and then the funny stuff in between that Dynamo can see.

End game? Be better setup for when I eventually do bother with .IFC.


BTW: a correction (for googling) for the above; it was the REST protocol, not the POST protocol...
The Building Coder: Revit Server REST API
I have always found the point-of-entry (of pretty-much-everything) on Jeremy's blog to be multiple-steps ahead of my starting point, but you may have more luck

A quick revisit of recent threads reveals there may be developments on the topic... in particular:
The Building Coder: RVT Properties to XLS and Forge Accelerators
which exploits another platform I've to really investigate (Forge)


EDIT
Do stick around Billy, it's good to have the occasional meaty chat on "more-than-modelling" matters. :thumbsup: