I have an excel file where it is possible to change the data:
In revit this data field is driven by a key schedule:
In dynamo I read the data from the excel file, this data field are strings.
How can I push back this data to revit, known this data field is driven by a key schedule.
This parameter should be created as a text. Please make sure of that. Hopefully, it will solve the problem, I think.
Sadly not, I added a printscreen from the key schedule in my original post
what is the data type the parameter crated?
You need to set the key (an element) not set the value. I don’t recall how, but I believe this will require you step into the API rather than using the simple workflow you’re aiming for.
The real question, is why are you doing this?
What you have done so far:
From where I stand there is a problem with step 3 (data is likely out of date), and step 5 isn’t straight forward. Why not just do whatever alterations you were going to do in Excel with the model content you see at step 2?
Why we’re doing this:
This isn’t just about a single field—we’re dealing with a complete door schedule. The goal is to make it editable by the project leader, who doesn’t work in Revit. We export the schedule to Excel so they can fill in or modify data (like door types, notes, fire ratings, etc.). Then I use a Dynamo script to push the updated data back into Revit.
Why not edit directly in Revit?
Because the person updating the data doesn’t use Revit. The Excel workflow gives them a familiar environment to review and input key information. It also supports batch editing, filtering, commenting.
On step 3 being problematic:
You’re right, the exported data can get outdated. But that’s an accepted limitation. We mitigate it by re-running the export before making major updates. It’s not perfect, but it’s manageable, and in practice the updates happen in coordinated review phases.
I found the solution 
Which was?
