<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Creating a &amp;quot;Simple List&amp;quot; Schedule in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/Creating-a-quot-Simple-List-quot-Schedule/m-p/254989#M33300</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;First time post, but from a long time lurker: &lt;BR /&gt;
 &lt;BR /&gt;
I am currently in the process of converting my firm's schedules from totally analog Excel files into AC19's Interactive Schedules. After some work, I am getting really close to achieving a satisfactory level of functionality. There is only one major catch at this point. &lt;BR /&gt;
 &lt;BR /&gt;
Is it possible to have a schedule function as a "simple list"?  &lt;BR /&gt;
 &lt;BR /&gt;
As an example, we would typically have our window schedule, followed by a "Specifications" section and a "Notes" section. The same can be said for our door schedule.  &lt;BR /&gt;
 &lt;BR /&gt;
I have found a pseudo-workaround, but it really is not working that well. Does anyone else have a better method? The fear behind keeping this small portion in Excel and continuing to simply import the image is purely for the sake of uniformity.&lt;/T&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;IMG src="http://community.graphisoft.com/t5/image/serverpage/image-id/74815i42FCF39041FF5CFF/image-size/large?v=v2&amp;amp;px=999" border="0" alt="Sample SChedule.jpg" title="Sample SChedule.jpg" /&gt;</description>
    <pubDate>Mon, 01 Feb 2016 17:23:46 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2016-02-01T17:23:46Z</dc:date>
    <item>
      <title>Creating a "Simple List" Schedule</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Creating-a-quot-Simple-List-quot-Schedule/m-p/254989#M33300</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;First time post, but from a long time lurker: &lt;BR /&gt;
 &lt;BR /&gt;
I am currently in the process of converting my firm's schedules from totally analog Excel files into AC19's Interactive Schedules. After some work, I am getting really close to achieving a satisfactory level of functionality. There is only one major catch at this point. &lt;BR /&gt;
 &lt;BR /&gt;
Is it possible to have a schedule function as a "simple list"?  &lt;BR /&gt;
 &lt;BR /&gt;
As an example, we would typically have our window schedule, followed by a "Specifications" section and a "Notes" section. The same can be said for our door schedule.  &lt;BR /&gt;
 &lt;BR /&gt;
I have found a pseudo-workaround, but it really is not working that well. Does anyone else have a better method? The fear behind keeping this small portion in Excel and continuing to simply import the image is purely for the sake of uniformity.&lt;/T&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;IMG src="http://community.graphisoft.com/t5/image/serverpage/image-id/74815i42FCF39041FF5CFF/image-size/large?v=v2&amp;amp;px=999" border="0" alt="Sample SChedule.jpg" title="Sample SChedule.jpg" /&gt;</description>
      <pubDate>Mon, 01 Feb 2016 17:23:46 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Creating-a-quot-Simple-List-quot-Schedule/m-p/254989#M33300</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-02-01T17:23:46Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a "Simple List" Schedule</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Creating-a-quot-Simple-List-quot-Schedule/m-p/254990#M33301</link>
      <description>I would make 2 schedules, one for the Top part and one for the Second one. The specifications and notes I would create an extra IFC field for them so that they are linked to the objects and then show up in the schedule.&lt;BR /&gt;
&lt;BR /&gt;
As another alternative I would include those fields for the objects in the first schedule so that they are part of it (even though they are repeated in every line) instead os creating the other schedule.</description>
      <pubDate>Mon, 01 Feb 2016 18:46:29 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Creating-a-quot-Simple-List-quot-Schedule/m-p/254990#M33301</guid>
      <dc:creator>Eduardo Rolon</dc:creator>
      <dc:date>2016-02-01T18:46:29Z</dc:date>
    </item>
  </channel>
</rss>

