https://community.graphisoft.com/t5/Collaboration-with-other/Accessing-components-and-descriptors-from-schedule/m-p/37563#M3284 <DIV class="actalk-migrated-content"><T>It would be quite useful to be able accessing components and descriptors in schedule. For example having the property object linked to a wall could show firerating descriptor and a basic description in the wall schedule.<BR /> At the moment we can access the name of the particular property object only but that's it AFAIK.<BR /> my idea is to have the property object named to our wall code, with all info in it (as I have mentioned - firerating, short description etc..) and get that listed in the schedule ( we are using index of used walls on plans in the documentation stages) rather than in a static component report.<BR /> the property name linked to eg wall is accessible for labels in GDL script so I just wonder if we could get that extended to components and descriptors at this level as well.<BR /> or is there any other way how to achieve this?</T></DIV> Fri, 21 Jul 2006 07:47:37 GMT Rob 2006-07-21T07:47:37Z https://community.graphisoft.com/t5/Collaboration-with-other/Accessing-components-and-descriptors-from-schedule/m-p/37563#M3284 <DIV class="actalk-migrated-content"><T>It would be quite useful to be able accessing components and descriptors in schedule. For example having the property object linked to a wall could show firerating descriptor and a basic description in the wall schedule.<BR /> At the moment we can access the name of the particular property object only but that's it AFAIK.<BR /> my idea is to have the property object named to our wall code, with all info in it (as I have mentioned - firerating, short description etc..) and get that listed in the schedule ( we are using index of used walls on plans in the documentation stages) rather than in a static component report.<BR /> the property name linked to eg wall is accessible for labels in GDL script so I just wonder if we could get that extended to components and descriptors at this level as well.<BR /> or is there any other way how to achieve this?</T></DIV> Fri, 21 Jul 2006 07:47:37 GMT https://community.graphisoft.com/t5/Collaboration-with-other/Accessing-components-and-descriptors-from-schedule/m-p/37563#M3284 Rob 2006-07-21T07:47:37Z https://community.graphisoft.com/t5/Collaboration-with-other/Accessing-components-and-descriptors-from-schedule/m-p/37564#M3285 We are looking at setting up our door schedules to be mainly Archicad based, using Propery Objects to assign hardware and notes to doors.<BR /> <BR /> The only issue I'm having at the moment is the criteria available to the I.S and List Schemes methods seem to be different and neither seems to have all the criteria we require. For example the I.S has <I></I><S><I><I></I></I></S>From Zone<E></E> and <I></I><S><I><I></I></I></S>To Zone<E></E> criteria for Doors whilst the List Schemes doesn't (that i can find), and the List Schemes allows you to list out all Components/Descriptors assigned to an element whilst the I.S doesnt ... <IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_confused.gif" style="display : inline;" /> <BR /> <BR /> I would prefer to set up a single I.S for editing and publishing (.txt into Excel), but as it stands i need to create a second Element List Scheme for publishing in order to get the Components/Descriptors containing the hardware info, notes etc.<BR /> <BR /> Not sure why it is this way .. i think the listing criteria should be consistent across both methods (therefore making List Schemes redundant really ..)<BR /> <BR /> Very interested to hear how you go with accessing Component/Descriptor info from associative labels. We are looking at this next for our wall codes and labeling. I had <I></I><S><I><I></I></I></S>assumed<E></E> it was possible ... Mon, 28 Aug 2006 05:58:43 GMT https://community.graphisoft.com/t5/Collaboration-with-other/Accessing-components-and-descriptors-from-schedule/m-p/37564#M3285 owen 2006-08-28T05:58:43Z