<?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: Document.Settings.Categories behaviour in loops in Revit API Forum</title>
    <link>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8809410#M42162</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Dear Khaled,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you for your update, sample model and important note on the two German categories.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;That sounds like a very likely cause for confusion.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I logged the issue &lt;U&gt;&lt;STRONG&gt;REVIT-148044&lt;/STRONG&gt;&lt;/U&gt; [OST_Views is missing when iterating over all categories in German Revit -- 15384477] with our development team for this on your behalf as it requires further exploration and possibly a modification to our software. Please make a note of this number for future reference.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You are welcome to request an update on the status of this issue or to provide additional information on it at any time quoting this change request number.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This issue is important to me. What can I do to help?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This issue needs to be assessed by our engineering team and prioritised against all other outstanding change requests. Any information that you can provide to influence this assessment will help. Please provide the following where possible:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN&gt;Impact on your application and/or your development.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;The number of users affected.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;The potential revenue impact to you.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;The potential revenue impact to Autodesk.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Realistic timescale over which a fix would help you.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;In the case of a request for a new feature or a feature enhancement, please also provide detailed Use cases for the workflows that this change would address.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This information is extremely important. Our engineering team have limited resources, and so must focus their efforts on the highest impact items. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Jeremy&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 23 May 2019 06:35:18 GMT</pubDate>
    <dc:creator>jeremytammik</dc:creator>
    <dc:date>2019-05-23T06:35:18Z</dc:date>
    <item>
      <title>Document.Settings.Categories behaviour in loops</title>
      <link>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8802354#M42159</link>
      <description>&lt;P&gt;So I was trying to get the localized versions of the categories and I noticed that I lost one category when switching from English Revit to German one.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For some reason, I don't get the "Views" category "OST_Views" in German Revit, here is a snippet to explain:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;            var isFound1 = doc.Settings.Categories.get_Item(BuiltInCategory.OST_Views);
            var isFound2 = false;
            foreach (Category category in doc.Settings.Categories)
            {
                if (category.Id.IntegerValue == (int)BuiltInCategory.OST_Views)
                {
                    isFound2 = true;
                }
            }&lt;/PRE&gt;
&lt;P&gt;Results (For the same test model):&lt;BR /&gt;English Revit: isFound1 = isFound2 = true;&lt;BR /&gt;German Revit: isFound1 = true, isFound2 = false;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is this is a bug induced only in loops?&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2019 15:31:46 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8802354#M42159</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-20T15:31:46Z</dc:date>
    </item>
    <item>
      <title>Re: Document.Settings.Categories behaviour in loops</title>
      <link>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8803703#M42160</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Dear Khaled,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you for your query.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Looking at your code, I have a question:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;How can `isFound1` ever have a value equal to `true`?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;It is set to a Category object. `true` and `false` are not Category object instances.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Anyway, this does indeed sound like a potential problem.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Could you please provide a minimal reproducible case for me to share with the development team so they can analyse what is going on?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://thebuildingcoder.typepad.com/blog/about-the-author.html#1b" target="_blank"&gt;https://thebuildingcoder.typepad.com/blog/about-the-author.html#1b&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Does the behaviour you describe occur in the same model, opened with different language versions of Revit?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Or are you looking at two different models?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Jeremy&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2019 06:46:39 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8803703#M42160</guid>
      <dc:creator>jeremytammik</dc:creator>
      <dc:date>2019-05-21T06:46:39Z</dc:date>
    </item>
    <item>
      <title>Re: Document.Settings.Categories behaviour in loops</title>
      <link>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8804997#M42161</link>
      <description>&lt;P&gt;Dear Jeremy,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sorry about the '&lt;SPAN&gt;isFound1' but I hope the idea was clear.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The models that were used for testing were a new empty model from the 'Construction Template'&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, please find attached a command to highlight the issue, running this command in ENG/DEU Revit will give different results as explained in the topic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My first guess is that it has something to do with the fact that we have 2 different categories called 'Ansichten' in German Revit mapped to both 'OST_Views' and 'OST_Elev', unlike the English Revit. Maybe that what causes the issue.&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2019 15:07:18 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8804997#M42161</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-21T15:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: Document.Settings.Categories behaviour in loops</title>
      <link>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8809410#M42162</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Dear Khaled,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you for your update, sample model and important note on the two German categories.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;That sounds like a very likely cause for confusion.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I logged the issue &lt;U&gt;&lt;STRONG&gt;REVIT-148044&lt;/STRONG&gt;&lt;/U&gt; [OST_Views is missing when iterating over all categories in German Revit -- 15384477] with our development team for this on your behalf as it requires further exploration and possibly a modification to our software. Please make a note of this number for future reference.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You are welcome to request an update on the status of this issue or to provide additional information on it at any time quoting this change request number.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This issue is important to me. What can I do to help?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This issue needs to be assessed by our engineering team and prioritised against all other outstanding change requests. Any information that you can provide to influence this assessment will help. Please provide the following where possible:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN&gt;Impact on your application and/or your development.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;The number of users affected.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;The potential revenue impact to you.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;The potential revenue impact to Autodesk.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Realistic timescale over which a fix would help you.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;In the case of a request for a new feature or a feature enhancement, please also provide detailed Use cases for the workflows that this change would address.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This information is extremely important. Our engineering team have limited resources, and so must focus their efforts on the highest impact items. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Jeremy&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 06:35:18 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8809410#M42162</guid>
      <dc:creator>jeremytammik</dc:creator>
      <dc:date>2019-05-23T06:35:18Z</dc:date>
    </item>
    <item>
      <title>Re: Document.Settings.Categories behaviour in loops</title>
      <link>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8809501#M42163</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;SPAN&gt;Jeremy for logging the issue, I think it doesn't have a big impact on development as there are other workarounds for iterating through the categories, so the impact in my case at least is minimal because I was just using it for collecting data.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 07:31:09 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8809501#M42163</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-23T07:31:09Z</dc:date>
    </item>
    <item>
      <title>Re: Document.Settings.Categories behaviour in loops</title>
      <link>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8809586#M42164</link>
      <description>&lt;P&gt;Thank you for your appreciation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, as long as&amp;nbsp;OST_Views and OST_Elevations can be told apart reliably, I suppose all is well in the end.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 08:15:33 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8809586#M42164</guid>
      <dc:creator>jeremytammik</dc:creator>
      <dc:date>2019-05-23T08:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: Document.Settings.Categories behaviour in loops</title>
      <link>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8819222#M42165</link>
      <description>&lt;P&gt;The development team closed&amp;nbsp;REVIT-148044 as Code Fix Needed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A new issue&amp;nbsp;REVIT-148265 has been opened to fix it in a future release.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please make a not of the new number.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for reporting this!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Jeremy&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 May 2019 17:35:48 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-api-forum/document-settings-categories-behaviour-in-loops/m-p/8819222#M42165</guid>
      <dc:creator>jeremytammik</dc:creator>
      <dc:date>2019-05-28T17:35:48Z</dc:date>
    </item>
  </channel>
</rss>

