The values come from the same .dbc file you use for Databook. Can you provide a picture?
Here an example:
i want to change a capacitor from device CCS000502-1 to CCS000502 that is an equivalent capacitor with different firm code
As soon i open the Properties window this is the content:
If i click on "Library only" the content doesn't change (All the "New Value" fields remain in <Delete Property>)
If i click on "Schematic Wins" the content change in:
In the "New Value" fields i have the same values of the "Old Value" fileds.
If i click on "Library Wins" the content doesn't change again. I see the same content of the previous image. So in the "New Value" fileds nothing is updated with the new infos (the DEVICE property is still CCS000502-1 and not CCS000502).
At this point i need to update manually every single properties and than proceed to the replace.
The property substitutions are based on what is set as 'Annotate' in the Databook configuration so you should check in there to see if there is any issue, though I would expect the properties on the symbol which is being replaced would have had these applied based on those same settings. If you cannot resolve this then contact your local support.
Hi Robert. The problem still remain.
What are the correct settings to make "Replace Part" function work?
Impossible to answer without your configuration, you should contact your local support for this, Communities is not the place to debug such issues. Does Databook/Search work correctly when placing parts?
I did some tests. If i drag&drop the symbol from the databook symbol preview window to the "Replacement part Number" field (instead of type the new code), the new properties are loaded correctly, but the symbol of the new component (always a capacitor with same symbol and same symbol name) is not recognized. So i'm not able to make the pin assigment.
I have a question related to the Property Mapping.
Is it possible to add a property to the list? We would like to have the Symbol Name property listed here too.
We ran into the issue that when another symbol name is used for initial placement, the replace action exchanges it with the default symbol name. Probably the added Symbol Name property could be a solution.