<?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: Working around the limitations of Property Expressions in Collaboration with other software</title>
    <link>https://community.graphisoft.com/t5/Collaboration-with-other/Working-around-the-limitations-of-Property-Expressions/m-p/289087#M37800</link>
    <description>I think you can only work with a fixed set of parameters and properties in the Expression Editor.&lt;BR /&gt;
&lt;BR /&gt;
That said, if you would make a list of 'element' costs properties for m1, m2, m3, piece etc, in theory you would be able to make schedules with costs if you fill out those fields in ArchiCAD.&lt;BR /&gt;
&lt;BR /&gt;
However I find it quicker to fill out the quantities in Excel, derived from a well set up schedule, since there still are quite a few things that need to be taken in to consideration for costs, that make little sense to model.&lt;BR /&gt;
&lt;BR /&gt;
One way or the other, you are inputting data / numbers in to a field of text/data. Favourites would streamline some of this, but in practice during design, things get changed around quite a bit, and whatever was put there from a favourite settings (cost per m2 or such) will likely have changed by the time you get to the cost calculation phase.&lt;BR /&gt;
&lt;BR /&gt;
While it is possible to get data in to an object from a text file or such, I think this method is a bit crude, but maybe someone with more experience can help out here.&lt;BR /&gt;
&lt;BR /&gt;
Going back and forth between excel and archicad schedule with Properties is working quite fast, unless you are trying to import back a spreadsheet with a few hundred fields of properties.</description>
    <pubDate>Thu, 28 Feb 2019 12:23:23 GMT</pubDate>
    <dc:creator>Erwin Edel</dc:creator>
    <dc:date>2019-02-28T12:23:23Z</dc:date>
    <item>
      <title>Working around the limitations of Property Expressions</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Working-around-the-limitations-of-Property-Expressions/m-p/289086#M37799</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I'm trying to see if I can work around some limits regarding the new Formula expressions for Properties, which seem to only allow calculations based on the built-in element attributes along with hard-coded numbers. &lt;BR /&gt;
&lt;BR /&gt;
Does anyone know:&lt;BR /&gt;
Is there a way for a Property formula to pull data from a standard GDL parameter of a library part OR the Property Object associated with an element, and use it in a formula expression? &lt;BR /&gt;
&lt;BR /&gt;
Also, is there a way to use a Global GDL script to pull data from a CSV or Text file and make it available in a global array that could be queried and accessed in other GDL scripts? &lt;BR /&gt;
&lt;BR /&gt;
These are the ideas I have for possibly accessing external databases of cost information to get cost reports within ARCHICAD.&lt;BR /&gt;
&lt;BR /&gt;
Thanks in advance to anyone who can give me a clue about how or whether these things are possible.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 27 Feb 2019 19:58:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Working-around-the-limitations-of-Property-Expressions/m-p/289086#M37799</guid>
      <dc:creator>Eric Bobrow</dc:creator>
      <dc:date>2019-02-27T19:58:32Z</dc:date>
    </item>
    <item>
      <title>Re: Working around the limitations of Property Expressions</title>
      <link>https://community.graphisoft.com/t5/Collaboration-with-other/Working-around-the-limitations-of-Property-Expressions/m-p/289087#M37800</link>
      <description>I think you can only work with a fixed set of parameters and properties in the Expression Editor.&lt;BR /&gt;
&lt;BR /&gt;
That said, if you would make a list of 'element' costs properties for m1, m2, m3, piece etc, in theory you would be able to make schedules with costs if you fill out those fields in ArchiCAD.&lt;BR /&gt;
&lt;BR /&gt;
However I find it quicker to fill out the quantities in Excel, derived from a well set up schedule, since there still are quite a few things that need to be taken in to consideration for costs, that make little sense to model.&lt;BR /&gt;
&lt;BR /&gt;
One way or the other, you are inputting data / numbers in to a field of text/data. Favourites would streamline some of this, but in practice during design, things get changed around quite a bit, and whatever was put there from a favourite settings (cost per m2 or such) will likely have changed by the time you get to the cost calculation phase.&lt;BR /&gt;
&lt;BR /&gt;
While it is possible to get data in to an object from a text file or such, I think this method is a bit crude, but maybe someone with more experience can help out here.&lt;BR /&gt;
&lt;BR /&gt;
Going back and forth between excel and archicad schedule with Properties is working quite fast, unless you are trying to import back a spreadsheet with a few hundred fields of properties.</description>
      <pubDate>Thu, 28 Feb 2019 12:23:23 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Collaboration-with-other/Working-around-the-limitations-of-Property-Expressions/m-p/289087#M37800</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2019-02-28T12:23:23Z</dc:date>
    </item>
  </channel>
</rss>

