My first thought was a nested light fixture would need to be used and that it would need to be "shared". I thought shared because we have to nest multiple fixtures in a chandelier to create multiple lamp light sources...and they need to be shared for them to render. At least that's how I remember it. Turns out using a "shared" nested light fixture has a pretty weird outcome when used in a baluster and applied to a railing.
See the light light off to the left of the railing? That's the nested shared light fixture family. It's locked and aligned to the side of a baluster yet only one light fixture shows up...a little farther away from the baluster than I expected it to be. That and there's only ONE, despite the number of baluster you can plainly see. Even stranger is that I can select the fixture and move it independently from the railing. I can move it next to the railing, but there is still only one.
This time I made a couple changes. I remove the "shared" status of the light fixture and reload/rebuilt it all because Revit hates switching between shared and not shared status. The result is a bit more like what I expected this time.
Even better, it renders each fixture!
I hope the LaM treats his minion well after sorting this out?
If you'd like to see a video of the lair you can check it out at You Tube. It demonstrates some yet to be disclosed real time collaboration environment too.