I have a bunch of MFG parts that have the MFG entered in different ways. Ie Wago vs WAGO or TE vs TE Connectivity
I went in the database and corrected this. But when I run Update Project Data it shows that all parts match and Update does not need run.
What is the proper process to update all MFG information in a project to the current information in the database?
You can see below that it shows 2 versions of Wago in my bom report, but the updater says that the MFG parts do not need updated.
The intent of that is to push library changes into a project if the part/cable/symbols were already in use and you've since made changes to those items in the library, instead of having to update them/reassign one by one. I've done this dozens of times, so this should work if you've edited a part in your Manufacturer Parts Manager in the Library tab, unless you've added circuits/terminals to the part, then it can't update the data. Pretty sure updating a cable that has added/subtracted cores would behave the same way, but I could be wrong.
Ya I would think the exact same thing.
In this situation, i had a terminal slice that i had entered as WAGO as the MFG. Then at some point after placing a ton of them I realized it and changed it to Wago (capitalization change) and continued placing them.
Now I want to go back and update the data to have them all come out on my BOM as Wago and the part is not showing up to be updated.
For completeness I also changed the MFG to SHAFFER to make sure it wasnt just getting tripped up on the Capitalization part.
1) Update Data
2) Next
3) Un Check everything but MFG parts and Next
4) Some parts show up, but not the one I want and all have Green Check Marks. (I am looking for Reference 2002-1201 because it was one of the ones that had WAGO originally)
5) Next
6) Finish
Then everything is the same. I am not sure what I am missing?
Maybe I need to contact my VAR and have them walk me through it.
Try doing something else that might trigger an update change. Change the description slightly, add current rating to it. My guess is that it isn't expecting changes to be done to the manufacturer, and isn't looking there for differences. When it does go populate the new description info, it will hopefully also grab the manufacturer name and push it too. You can try changing something having to do with the terminals, but be careful you don't end up disassociating all of your cables or something. I believe it does not look at the description for a terminal (maybe the mnemonic, possibly the terminal number?) when it looks for changes.
This may be a silly question, but you re-render (update) your report drawings?
I tried changing :
A) Description
B) Circuit
C) MFG PN
D) MFG
But no change in placed components.
and not a silly question, Evan I did make sure to update the report drawing.
I guess I will contact the Var and see what they think
It's used to update old data in Project according to the application data. All your screenshots seems to be ok, so maybe there is a bug but without your data, I cannot confirm it.
Please contact with your VAR
Update
I talked to the VAR and it does seem like it is a(nother) bug that is present in 2018 SP4. I am not sure when it started.
I will update with the SPR.
I did test symbol update and that works.
Hi Matt,
Can you reproduce the issue in a Little Project with just one component? if so, can you share with me the Project and the original part (the ona saved in library->manufacturer part)
Miguel
Does it work for you Miguel? Are you on 2018 SP4?
It should be pretty easy to try it on any project that you already have.
Hi,
I have tested it in 2019 beta with your report (adding the new fields shown in the image) and with a projwct done by me.
Although I tested in a higher version, none bug relative to navigate has been reported in sp4.
I have gotten it to propagate symbol and manu part changes. However it will randomly declare that two items don't match and thus can't be updated when the entire point is usually that I want it to overwrite the differences to make everything match. It really needs an override for those cases.