Thank you for your response. It partially makes sense to me.
I’m still a bit confused about the behavior of the Documents in this specific document.
When connected to a Panel it shows 29 items - the same as Links. But when connected to a Value PickerDocuments only shows 13 items.
When selecting an item from the Documents with the Value Picker the output is more than the selected item. Is this because of the class and/or nested linked files?
Finally, when inspecting project infomation such as Project Base Point and Survey Point from the same filename, the values are not identically. Am I inspecting the yellow filename or green filename?
Correct, I believe these are generated for Datatree matching, typically you would only need 1 of the Document output (which you are trying to get via value picker, List item would be the component in that case)
Those can be different in the various documents. I’ll try and recreate your situation to verify or you can post a small example.
Thank you for your response and your time spent looking into this.
I’ve tried to recreate the problem in a smaller Revit-file and linked it into an empty Revit-file.
A few things are going on here, where I can’t quite follow the logic behind it.
I have two simple Revit-files PBP_SP_TEST_01 and PBP_SP_TEST_02. 01 is linked into 02. (See attached)
The first thing to note is the behaviour of the Value Picker and Project Location components. When the linked Revit-file is selected from Links, the input in Project Location is for some reason my open project, PBP_SP_TEST_02 and not the selected linked project?
When selected from Documents the correct project is used as input.
The second thing to notice, is the difference between the coordinates of SP/PBP and the inspected values of E/W and N/S. This difference is probably caused by the logic behind the Survay Point in Revit. By unclipping the Survey Point, you can move the point without changing the E/W and N/S values. The xyz position is however still affected. This is the root of a lot of trouble in project coordination, and I have yet to see the benefit of this workflow.
The third thing to notice, is how the Project Base Point infomation is unavailable from the linked project.
@Japhy maybe you can clarify if all of this is expected behaviour from the components in relation to the class?
Thanks, for the example, i’ll dig into it as soon as i can. I’ve gone down these roads a few times but not often enough to remember exactly how it all works in Revit.