Saving/Mapping Spacedesign attributes

So far my Evaluation of Space Design went pretty well and I think this might be the right choice for my company.

Now there is one problem left I'm facing, and that is saving space design attributes so I can just start up a new drawing, import some components and immediately have cost/weight/etc ready for reporting, but the SD attributes are not saved in a component like the DC attributes are. I've seen a bunch of topics about this, all without answer though.

Now actually I already have my solution for this, as I can just save a cost/weight/etc DC attribute in my component and then map that attribute to the according SD attribute, already tested it and it works like a charm. The problem would be to save the mapping, because neither with reloading a saved .sda nor a saved .sds do I get the mapping back. My mistake or is there no way to save the mappings currently?

Replies

Rich Hart July 1, 2014 at 4:39am

I mapped DC:lenx to Cost

And then save that as my project attributes:

Then all I need to do is Load from Project before making the report, and that works for me. I get the lenx value reported as my cost.

Is that similar to what you are trying to do? or is the mapping that you are doing something else?
- Bernhard Hockertz > Rich Hart July 1, 2014 at 9:24pm
  
  I used the Map Attributes button which is in the same window:Actually your way of Mapping (%DC: [attribute name]%) doesn't work for me, whereas mapping the attributes like this works normally. I just have no way to save that setting apparently, save/load to/from project doesn't work either.
  
  Originally I tried mapping the way you described, but when it didn't work I assumed that was not the way to do it and used Map Attributes, but now I'm confused why I get a different result when doing the same thing.
  - Rich Hart > Bernhard Hockertz July 2, 2014 at 9:25am
    
    In order to save SpaceDesign attributes on SketchUp components, so that when you place a component it will have a specific default attribute like Cost, you need to either learn to use the Ruby interface to place the attribute on the model before you save it as a component, or use the Create Attributes for Components dialog:
    
    This works by having all of the components in a local collection in one model and saving a CSV file of the attributes that you can use to change the SpaceDesign attributes for the components before you save, or resave, them as a local collection. Once this is done, when you place those components from the collection, they will have the saved attributes, but still can be over-ridden on instances of the component placed in the model.
    
    This is explained here:
    
    http://www.renderplus.com/wp2/wk/Auto_Generate_Attributes.htm
    
    I just tested this, and found that I had broken this last week, when I added that fix for the Locale number and currency settings, so I posted a new version, NG02, that you will need to install before seeing if this works for you.
    
    However, I think you what you need is a solution that will generate the attributes based on the Dynamic component attributes. Could you post a couple of components that I could use to see why mapping or simply assigning the dynamic attribute to another attribute doesn't work for you?
    
    You can email them to me at rich.hart@renderplus.com
    
    Then I can place them and see why the attributes and mappings are not being saved. This is something that definitely needs to work.