<?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: Exporting Material properties to Excel - Python Script in Archicad Python API</title>
    <link>https://community.graphisoft.com/t5/Archicad-Python-API/Exporting-Material-properties-to-Excel-Python-Script/m-p/325840#M147</link>
    <description>&lt;P&gt;I do follow your opinion but in this case, exporting properties through python would be just one step of a whole proces. A proces to sustainability that could be automated. And that's why here, there's no other way than to use python.&lt;/P&gt;</description>
    <pubDate>Thu, 30 Dec 2021 16:17:00 GMT</pubDate>
    <dc:creator>Ssc_97</dc:creator>
    <dc:date>2021-12-30T16:17:00Z</dc:date>
    <item>
      <title>Exporting Material properties to Excel - Python Script</title>
      <link>https://community.graphisoft.com/t5/Archicad-Python-API/Exporting-Material-properties-to-Excel-Python-Script/m-p/325622#M145</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just started couple of months ago finding my way with python in Archicad 24. I have some experience in python but definitely not enough as I keep having different problems with the export script (the one provided by Graphisoft).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With the basic script you can export Element properties very easily to an excel sheet. But as soon as I change the script to get a random material property, the script gives an error. The material property is randomly chosen after getting the full list with python as well. The last line has been added to get the 'Material Property'.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;propertyUserIds = [
    act.BuiltInPropertyUserId("General_ElementID"),
    act.BuiltInPropertyUserId("General_Height"),
    act.BuiltInPropertyUserId("General_Width"),
    act.BuiltInPropertyUserId("General_Thickness"),
    act.UserDefinedPropertyUserId([
        "COMBUSTION (Materials)", "CO2 Content"])
]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;By running this in Archicad we get a lot of errors with the following errorcode as the last: &lt;STRONG&gt;&lt;EM&gt;"propertyId cannot be initialized with &amp;lt;class 'Archicad.releases.ac24.b3000types.ErrorItem'&amp;gt; "&lt;/EM&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Am I doing something wrong when changing the script or is export with python on the level of 'materials' not supported yet?&lt;/DIV&gt;</description>
      <pubDate>Mon, 27 Dec 2021 14:36:58 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-Python-API/Exporting-Material-properties-to-Excel-Python-Script/m-p/325622#M145</guid>
      <dc:creator>Ssc_97</dc:creator>
      <dc:date>2021-12-27T14:36:58Z</dc:date>
    </item>
    <item>
      <title>Re: Exporting Material properties to Excel - Python Script</title>
      <link>https://community.graphisoft.com/t5/Archicad-Python-API/Exporting-Material-properties-to-Excel-Python-Script/m-p/325682#M146</link>
      <description>&lt;P&gt;IME, python is just a longhand work-around to make basic functions less effective... I'm sure the tool is useful, as I read enough people saying they use it for scripting template management, file migration, file maintenance functions. But it's beyond me why I should bother with python TBH&lt;/P&gt;</description>
      <pubDate>Tue, 28 Dec 2021 22:52:35 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-Python-API/Exporting-Material-properties-to-Excel-Python-Script/m-p/325682#M146</guid>
      <dc:creator>Patrick M</dc:creator>
      <dc:date>2021-12-28T22:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: Exporting Material properties to Excel - Python Script</title>
      <link>https://community.graphisoft.com/t5/Archicad-Python-API/Exporting-Material-properties-to-Excel-Python-Script/m-p/325840#M147</link>
      <description>&lt;P&gt;I do follow your opinion but in this case, exporting properties through python would be just one step of a whole proces. A proces to sustainability that could be automated. And that's why here, there's no other way than to use python.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Dec 2021 16:17:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Archicad-Python-API/Exporting-Material-properties-to-Excel-Python-Script/m-p/325840#M147</guid>
      <dc:creator>Ssc_97</dc:creator>
      <dc:date>2021-12-30T16:17:00Z</dc:date>
    </item>
  </channel>
</rss>

