I have just discovered very useful and probably not described functionality of Fusion Electronics. It is possible to make the component name (>VALUE) dependent on the search in library phrase. Functionality works a little bit randomly but anyway is useful for generic symbols, where the same symbol (like a diode) can be shared across many variants of that component - including different packages and footprints.
In my case for "demo" library: I have created single symbol with name "DEMO". Next I prepared 2 footprints DEMO and DEMO2 and next assigned them to component DEMO. Each of the footprints have to have its own attribute sets. Each of attribute set name will contain search phrase (real component name, eg DS18B20, DS18B20U etc). In case of my example, first variant of component has names "aaa" and "bbb" with corresponding VALUE set to "my_aaa" and "my_bbb". Second version of component has only one name "ccc" with corresponding value "my_ccc".
Since now, when we search for "aaa" or "bbb" in order to place component in schematic, we will find our component DEMO with preselected variant (in this case "ABC"). When component is placed anywhere of schematic, its >VALUE will be replaced by to searched phrase = attribute set name (AAA or BBB). If phrase "ccc" is used - we will get variant "DEF" with >VALUE set to "my_ccc".
Unfortunately there is a bug. Please refer numbers to attached screenshot.
1. I was searching for "aaa" phrase. Component DEMO was found. Component placed on schematic has >VALUE set to "my_aaa". That's ok.
2. Now I searching for "bbb". I found component DEMO again. But this time when component is placed on schematic, its name is wrong "my_aaa".
3. The workaround is searching for another component, eg "xxx" and place it on schematic. In this case it was SDE2506. I didn't test if placing is required. Maybe just searching for random phrase will be enough.
4. Now I searching for "bbb" again. Component DEMO was found. This time, when I place this component again on schematic, its name (>VAL:UE) will be properly set to: my_bbb
5. Next test: searching for "ccc" and placing component DEMO on schematic: description is "my_ccc" (variant name DEF"). In this case, the footprint will also change to related to DEMO2 package.
It seems that every searching for component should result of component name and its footprint change. Otherwise if only footprint changes but component name stays the same, wrong name (>VALUE) will be used.
