<?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: Problem with Attribute Manager layer set import in Project data &amp; BIM</title>
    <link>https://community.graphisoft.com/t5/Project-data-BIM/Problem-with-Attribute-Manager-layer-set-import/m-p/145478#M13308</link>
    <description>OK, I don't know what I did right this time, but after some 30 attempts that failed, THIS procedure worked:&lt;BR /&gt;
&lt;BR /&gt;
1. Imported just one layer set&lt;BR /&gt;
2. Opened up layers and &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;manually saved the current Custom set as new set&lt;E&gt;&lt;/E&gt; without clicking on the set imported above&lt;BR /&gt;
3. Went back to Attribute Manager and imported another *single* layer set using Overwrite&lt;BR /&gt;
4. Opened layers, and figured out that the second set is actually correct&lt;BR /&gt;
5. Went back to Attribute Manager and successfully imported all other layer sets using Overwrite.&lt;BR /&gt;
&lt;BR /&gt;
Here's a quote from email I got from our representative (thanks as always, Greg!), that explains why I kept failing with "Append":
&lt;BLOCKQUOTE&gt;If the file you brought across had layers which were not is exact numerical order for the in index values (for example, it had 1=Walls, 2=Floors, 3 was unused because it had been deleted, 4=Roofs) after "appending" the layers across you would not have the same index values (in the example you would end up with 1=Walls, 2=Floors and 3=Roofs). But a layer combination that originally showed the Walls and the Roofs but not the Floors (show layers with index values 1 and 4 only) would still try to show those index values (but since Roofs isn't 4 any more it would be incorrect).&lt;/BLOCKQUOTE&gt;

Hope that maybe helps somebody.</description>
    <pubDate>Fri, 12 Jun 2009 16:12:12 GMT</pubDate>
    <dc:creator>matjashka</dc:creator>
    <dc:date>2009-06-12T16:12:12Z</dc:date>
    <item>
      <title>Problem with Attribute Manager layer set import</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Problem-with-Attribute-Manager-layer-set-import/m-p/145477#M13307</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Hi All&lt;BR /&gt;
&lt;BR /&gt;
I didn't know which forum to put it, but this is kind of an "IT manager" problem, maybe this forum is OK.&lt;BR /&gt;
&lt;BR /&gt;
Since the last patch update 2675 (I'm stating this only because I've never had a problem with this before) &lt;B&gt;I am unable to correctly import layer sets from another project&lt;/B&gt;. In the Attribute Manager everything looks fine, but after I open the layer dialog box and click a layer set, the layer attributes in layer sets are totally wrong.&lt;BR /&gt;
&lt;BR /&gt;
I tried that a number of times with different files, and every time I get the same result: &lt;B&gt;wrong layer parameters in layer sets&lt;/B&gt;.&lt;BR /&gt;
The original file has them correctly - no mistake here, it's been quadruple-checked.&lt;BR /&gt;
&lt;BR /&gt;
I just created a completely new template, from scratch in AC12 - everything could be successfully merged except for the layer sets. I'm very reluctant to do this manually, but I have lost a lot of time already.&lt;BR /&gt;
&lt;BR /&gt;
Do you experience the same problem?&lt;BR /&gt;
&lt;BR /&gt;
I'm asking before I report a bug. THANKS!&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 26 May 2023 13:26:24 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Problem-with-Attribute-Manager-layer-set-import/m-p/145477#M13307</guid>
      <dc:creator>matjashka</dc:creator>
      <dc:date>2023-05-26T13:26:24Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with Attribute Manager layer set import</title>
      <link>https://community.graphisoft.com/t5/Project-data-BIM/Problem-with-Attribute-Manager-layer-set-import/m-p/145478#M13308</link>
      <description>OK, I don't know what I did right this time, but after some 30 attempts that failed, THIS procedure worked:&lt;BR /&gt;
&lt;BR /&gt;
1. Imported just one layer set&lt;BR /&gt;
2. Opened up layers and &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;manually saved the current Custom set as new set&lt;E&gt;&lt;/E&gt; without clicking on the set imported above&lt;BR /&gt;
3. Went back to Attribute Manager and imported another *single* layer set using Overwrite&lt;BR /&gt;
4. Opened layers, and figured out that the second set is actually correct&lt;BR /&gt;
5. Went back to Attribute Manager and successfully imported all other layer sets using Overwrite.&lt;BR /&gt;
&lt;BR /&gt;
Here's a quote from email I got from our representative (thanks as always, Greg!), that explains why I kept failing with "Append":
&lt;BLOCKQUOTE&gt;If the file you brought across had layers which were not is exact numerical order for the in index values (for example, it had 1=Walls, 2=Floors, 3 was unused because it had been deleted, 4=Roofs) after "appending" the layers across you would not have the same index values (in the example you would end up with 1=Walls, 2=Floors and 3=Roofs). But a layer combination that originally showed the Walls and the Roofs but not the Floors (show layers with index values 1 and 4 only) would still try to show those index values (but since Roofs isn't 4 any more it would be incorrect).&lt;/BLOCKQUOTE&gt;

Hope that maybe helps somebody.</description>
      <pubDate>Fri, 12 Jun 2009 16:12:12 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Project-data-BIM/Problem-with-Attribute-Manager-layer-set-import/m-p/145478#M13308</guid>
      <dc:creator>matjashka</dc:creator>
      <dc:date>2009-06-12T16:12:12Z</dc:date>
    </item>
  </channel>
</rss>

