I create a script to import data into shared parameter value of each family by marking every instance with a unique ID. It works for shared parameters that are defined by the “text” type. but it causes error for parameters that are defined with “integer” type.
any suggestion to solve it, or the way to simplify it?
thank you
attachement
Documentation
Try removing the “String from Object” for TKDN% assignment node since you set “Read All as String” to false. Or converting string to integer once again for TKDN% parameter assignment.
thank you so much bro, it solved
Bro, anyway it worked last night and it error again today, do you have other solution?
oh I need more info on the error, like what does the error message say. But essentially you need to ensure that the data type and parameter type match with each other.
I also attached link download script below
Doc To share
nah you want to hook elements to that parameter setting node, not a column of excel file. What you’ve achieved is correct, just make it consistent for all parameters.
try check the parameters storage type
I found an anomaly while working with my script across different devices.
I initially created the script on my office desktop (1st Device) at noon. Later that night, I attempted to remove "StringFrom.Object" using my personal laptop (2nd Device), and it worked. However, when I applied the script on my office desktop the next morning, errors appeared again.
To investigate further, I retried the script on my personal laptop at home, and it worked. But when I ran it on my personal desktop (3rd Device), I encountered the same errors as on my office desktop.
All devices are running Revit 2023, so I assumed they were the same. However, after checking the detailed version numbers, I found a difference:
To confirm if the issue was relatd to Revit Version 23.0.11.19, I also tested the script in Revit 2025 Version 25.1.0.44 that installed in my 2nd Device, and it worked without errors.
So, the first suggestion from @BimAmbit was actually correct. My temporary conclusion is that there is a bug in Revit 2023 Version 23.0.11.19
Thanks All
Hard to say without insight into what the first error is. I’d say most often it’s an excel update which has been applied to each system which has broken the API - a result of Microsoft’s update process which is very well known and documented but not fixed to date.
Try running the online office repair tool from Microsoft to see if it fixes things for you.
solved
