Although my script can write the path in the parameter to this file, then the file is linked only to the family, not integrated (baked). However, the lighting family should be passed on to customers and therefore no path may be in the parameter. The ies file has to be baked into the family.
The script works right at first glance. But the path is just a link. If you delete those files outside of Revit, then the family will not work either. But you can integrate the ies file exactly this way into the family. For this you have to press the button with the three dots and manually select the ies file.
Thanks for your help and sorry for my bad description.
But i don’t think your script works. The old ies file still seems to be stored in the parameter.
You can see this better on several types and ies files.
1.Now i try to set more than one ies file to a family type:
The script works. No error appears, but no ies file is assigned.
Remember If you dont reload the family after the set value… then will nothing be set in the “mother” file. And if you close the file, which would be obvious, then you need to reopen the graph every time. for testing purposes can you freeze the close node, but remember to turn it on again when leaving the graph turning it into production mode.
Following up on this, in case you want to know what was going wrong:
Fiesta, you are correct: It was NOT working, in the earlier Suggestions. But it wasn’t actually a Dynamo error that was happening, its how Revit works, with respect to IES files:
Your Revit.ini has a specific path to IES files. That’s the only way it will automatically “find them” by name only. Otherwise, it needs a full path.
So you’ll see in the two suggestions you got in the thread, one presents the IES name only, in the Set Parameter by name node, and the other presents the full path, at which point it is “found.” Coincidentally, if the IES file was in the location that was pathed on your machine, it may have worked with the earlier solution as well.
Sounds like a Revit issue, that masqueraded as a Dynamo issue (that then turned in to a personnel issue), but thankfully got solved anyway.
that’s true. in the Revit.ini is the path to the standard ies data. If one uses the “standard functions” of Revit, one can assign automatically also several types the suitable ies file. Unfortunately, this only sets a “link”. If another user does not have the same ies data under the same path. Then the family does not work anymore.
By hand, you can set the ies file but for each type (baking / integrate).
Well, it really seems to have been more of a revit problem.
Problem was solved.
A happy ending for all