Search the Community

maybe I completely misunderstand the workflow, but here is my problem: I have a library file, lets call it 'chairs'. This file has (as expected 😉) chairs as symbols, each symbol has a data set attached in the data manager. The complete mapping set is saved as 'mapping_chairs'. Also, there is a second library file, lets call it 'tables'. Same procedure with table symbols and a resulting mappig set called 'mapping_tables' Next I have a drawing that has exactly these chair and table symbols, but no mapping. Loading the 'mapping_tables' set leads to a correct mapping of all tables in the data manager and loads the correct data to the instances in the drawing. Loading the 'mapping_chairs' set afterwards will kill all mappings for the table symbols in the data manager, while correct data for the tables will remain in the drawing for the already drawn instances. But new instances wil get no data since there is no mapping available. or the other way around: I want to create a merged mapping called 'mapping_chairs_and_tables' in an empty drawing. I can either load 'mapping_chairs' or 'mapping_tables' but not both mappings. The only way to create a merged mapping is to import both library files with their respective symbols completely and save the mapping of this file as merged mapping. Does that make sense ???? Background: People send me files with symbols from the VWX Libraries. I have some dataset mappings for VWX libraries according to my workflow. So my wish is simply to map my datasets to these files and proceed working without exchanging symbols or even re-draw everything. The idea behind this is to work with the data in the VWX files, unregarded what the shape of the symbol/object/plugin looks like, as long as the correct data is attached to it. So as an extreme example, I have a circle in a drawing that is mapped to data that may describe the components of complete bathroom, and I can match this complete bathroom to another drawing where this bathrom symbol is not a circle, but a rectangle. In the end the VWX file in this way becomes a kind of DBMS (database management system). Or in other words: One drawing shows a Ford, another drawing shows a BMW, the third shows a VW, but for me as a tire-dealer, I am only interested in the mappings for the tire sizes.