Run Verify in DxDataBook after you replace the symbol. But, from the pictures it doesn't look like you are using DxDataBook. Without DxDataBook you will have to either delete the part and replace it to add all of the properties or manually edit the properties in the dialog. Another alternative would be to set up the PDB to 'back-annotate' these properties during package (it all depends on how you have your library set up).
1 of 1 people found this helpful
Wow, what a great description!
The first part was placed and properties annotated using DxDatabook. I could tell because of the DxDB_Libname property. If the property database is still available and connected you could RMB on the symbol, Load into DxDatabook. This should open Databook with the Resistor library. Some or all of the column headings may be filled, in the example below my part number has a property. I want to remove the condition or all conditions.
Next using the query builder I searched for the resistor value, I used 4.02k for this example. In this example I only had one 4.02k resistor, you may have more and you want to verify that the Cell Name is the same if the PCB is already created.
Use the Right Mouse Button over the correct value you want, and simply annotate unique, and the part properties should change to the desired properties. In this case R86 changed from 10k to 4.02k
When using DxDatabook, it is not recommended to use Replace Symbol to replace a resistor with a like resistor. Update PDB Properties on Symbol should also be UNCHECKED at ALL TIMES when using DxDatabook to manage properties.
Contact support or myself if you need more assistance. email@example.com
I have followed your instructions which work.
They change the part number, value and description fields for the component on the schematic.
However they do not change the Part Label field or Part Name field.
Also they now list the MPN1, MPN2, MPN3, Package, and manufacturer's fields more than once. One set of data is for the old part and the other set of data is for the new part.
Here is a picture showing the duplicate information.
I have package the design, with Update PDB Properties UNCHECKED as recommended. But this does not resolve these extra fields.
Currently we are using version 7.9.1. Therefore is this now just a bug in this release which is fixed in a later version?
I suggest you contact Customer Support to get quick resolution of this issue, Communities is monitored by users in different time zones, here in Europe and in Gary's case, in the U.S.
One thing to check on the duplicate properties is whether one of a pair is listed as 'non-common' in the properties dialog which would indicate it was added before it was properly defined, or whether one of the pair is a 'block value' whilst the other is an 'instance value'.
Having checked this contact your local support representative.
This method works in 9.3.1 although the steps and dialog look a little different, only a geek would notice the difference .