<?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 Re: WINDOW ORDER IN THE SCHEDULE in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/WINDOW-ORDER-IN-THE-SCHEDULE/m-p/120183#M12263</link>
    <description>&lt;BLOCKQUOTE&gt;cougarbrent wrote:&lt;BR /&gt;I LABEL MY WINDOWS A1,B1,C1,D1, ETC FOR MAIN LEVEL WINDOWS AND A2,B2,C2, ETC FOR UPPER LEVEL WINDOWS BUT IN MY SCHEDULE IT LISTS THEM IN ORDER LIKE THIS - A1,A2,B1,B2,C1,C2 ETC. I WANT THE FIRST FLOOR WINDOWS TO LIST FIRST IN THE SCHEDULE AND THE SECOND LEVEL WINDOWS TO COME AFTER IN THE SCHEDULE.&lt;BR /&gt;
&lt;BR /&gt;
i CANT FIGURE OUT WHAT I AM DOING WRONG.&lt;BR /&gt;
ANY HELP WOULD BE APPRECIATED.&lt;/BLOCKQUOTE&gt;

For fields for which you have enabled sorting (up or down arrow), they are sorted in order, top to bottom (field list) - left to right (schedule itself).  So, if you want things grouped by story, you must add the story to your field list and make it the first field.  Make it a 'title' field so that it displays only once for each story.  (I don't have AC running at the moment.  AC may call this a 'headline' field or something like that.)&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Karl</description>
    <pubDate>Tue, 31 May 2011 16:22:30 GMT</pubDate>
    <dc:creator>Karl Ottenstein</dc:creator>
    <dc:date>2011-05-31T16:22:30Z</dc:date>
    <item>
      <title>WINDOW ORDER IN THE SCHEDULE</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/WINDOW-ORDER-IN-THE-SCHEDULE/m-p/120182#M12262</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I LABEL MY WINDOWS A1,B1,C1,D1, ETC FOR MAIN LEVEL WINDOWS AND A2,B2,C2, ETC FOR UPPER LEVEL WINDOWS BUT IN MY SCHEDULE IT LISTS THEM IN ORDER LIKE THIS - A1,A2,B1,B2,C1,C2 ETC. I WANT THE FIRST FLOOR WINDOWS TO LIST FIRST IN THE SCHEDULE AND THE SECOND LEVEL WINDOWS TO COME AFTER IN THE SCHEDULE.&lt;BR /&gt;
&lt;BR /&gt;
i CANT FIGURE OUT WHAT I AM DOING WRONG.&lt;BR /&gt;
ANY HELP WOULD BE APPRECIATED.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 31 May 2011 16:05:02 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/WINDOW-ORDER-IN-THE-SCHEDULE/m-p/120182#M12262</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-05-31T16:05:02Z</dc:date>
    </item>
    <item>
      <title>Re: WINDOW ORDER IN THE SCHEDULE</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/WINDOW-ORDER-IN-THE-SCHEDULE/m-p/120183#M12263</link>
      <description>&lt;BLOCKQUOTE&gt;cougarbrent wrote:&lt;BR /&gt;I LABEL MY WINDOWS A1,B1,C1,D1, ETC FOR MAIN LEVEL WINDOWS AND A2,B2,C2, ETC FOR UPPER LEVEL WINDOWS BUT IN MY SCHEDULE IT LISTS THEM IN ORDER LIKE THIS - A1,A2,B1,B2,C1,C2 ETC. I WANT THE FIRST FLOOR WINDOWS TO LIST FIRST IN THE SCHEDULE AND THE SECOND LEVEL WINDOWS TO COME AFTER IN THE SCHEDULE.&lt;BR /&gt;
&lt;BR /&gt;
i CANT FIGURE OUT WHAT I AM DOING WRONG.&lt;BR /&gt;
ANY HELP WOULD BE APPRECIATED.&lt;/BLOCKQUOTE&gt;

For fields for which you have enabled sorting (up or down arrow), they are sorted in order, top to bottom (field list) - left to right (schedule itself).  So, if you want things grouped by story, you must add the story to your field list and make it the first field.  Make it a 'title' field so that it displays only once for each story.  (I don't have AC running at the moment.  AC may call this a 'headline' field or something like that.)&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Karl</description>
      <pubDate>Tue, 31 May 2011 16:22:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/WINDOW-ORDER-IN-THE-SCHEDULE/m-p/120183#M12263</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2011-05-31T16:22:30Z</dc:date>
    </item>
  </channel>
</rss>

