Updating component descriptions in Project Database for Reports

[jallenDBQ7U]

Can someone tell me the update command to force the project database to update component details on a set of drawings (if there is a command)?

Recently I have been working to add numerous items into the database catalog.  My main interest is to have Bill of Material reports show more descriptions so that I don't have to do manual edits in Excel.  My recent additions are not affecting the Bill of Material.  The newly added items in the database still show no details on the Report.

Also, is there a safe command for merging an external part catalog into the ACADE one?  The external one is fully compatible and has been used by others but there are likely some duplicates in it.  It may also be possible that some catalog numbers in it are in different FAMILY locations where duplicates do occur.

[james.mcmillanNYR6A]

BOM report pulls cat description by matching the manufacturer and catalog for the given family in the default cat. If no cat description is provided in the report it is not finding a match.

For a given item that does not have a description, if you edit component and catalogue check does it have the description? If not can you catalogue lookup and find the part you are looking for?

[james.mcmillanNYR6A]

Access has tools for merging databases, I would be sure to backup my working database before using it! There are options for overwriting or keeping duplicates, I have never had a problem with identical parts in different family tables

[alds02]

Could you tell us what happens if you do Edit Component >> Lookup, on one of these components that doesn't have details in the BOM? Does it go to the wrong table?

On occasion I have Multiple Catalog items that are pointed at the wrong table, and I never realize it until I run a BOM report. In fact, just yesterday it happened. It was the result of copying a component. The new one of course kept all the part information but somehow didn't keep the correct table in the multiple catalog item. I'd call it a bug if I could reproduce it reliably.

[jallenDBQ7U]

Here is an example of my problem.  I have two screen captures merged into one image below.  The first screen capture shows a part that was already in the database catalog and on my BOM report for the panel.  The second screen capture shows a part that was added to the catalog database but still not in my new BOM report. 

I can do an additional component edit after updating the catalog where I do catalog lookup and it will show the matching catalog part.  I then allow it to do update of the linked objects after I click OK button (child component and/or panel layout part drawings are opened).  Sometimes the description will then show-up on the BOM and sometimes it won't.  In this case it still doesn't show it on my BOM after doing this additional step.

[alds02]

You seem to be using the Panel BOM report, is that correct?

That same problem I described with a copied component somehow pointing at the wrong table, that can happen in panel footprints too. The schematic component is always working fine with the catalog, but if you are using the panel BOM report, ACADE is looking at the panel component instead. I am not sure why it happens but sometimes the panel footprint is not looking at the correct table in the catalog and so the BOM report is blank.

But I can't tell if that's what is happening in your case.

[jallenDBQ7U]

Yes.  This is for the panel BOM report. 

As another example, one of the panel items opens the catalog with an empty list for MISC_CAT even though FAMILY has a value of CB.  The component on the electrical schematic is also FAMILY CB and links directly to the correct matching part in the CB table.

MISC_CAT is supposedly default if no other table matches.   What is the simplest way to force all panel layout items to refresh this data to match schematics?  I don't want to open each component one by one.  There are too many.  When I do an update on the schematic sheets for components ACADE seems to think the panel footprints are okay unless I modify the component to trick the system.

[jallenDBQ7U]

Does the BOM report for panel look at the catalog for information to build the report or use its own database from the schematic list links?  On this part the schematic report gives descriptions.  The panel report shows blanks for descriptions.  I tried to correct it by selecting the schematic component a second time (note empty description in schematic list).  panel BOM report is still blank for descriptions for this item while schematic BOM report gives description for item in CB table. 

EDIT* Oops! I suddenly realized the description in this popup is local documentation for specific component rather than description from catalog.

[alds02 · Accepted solution]

You are correct that editing the schematic component will continue to cause the panel footprint to update, but doesn't push through the correct table.

This is one of the reasons I always prefer to finish the schematics first, and then use the schematic list to insert the panel footprints. That workflow seems to be the best way to keep this table lookup issue from happening. That's probably not the method you want to use right now, and I can't think of a fast way to fix your footprints.

[alds02]

---

@jallenDBQ7U wrote:

Does the BOM report for panel look at the catalog for information to build the report or use its own database from the schematic list links?  On this part the schematic report gives descriptions.  The panel report shows blanks for descriptions.  I tried to correct it by selecting the schematic component a second time (note empty description in schematic list).  panel BOM report is still blank for descriptions for this item while schematic BOM report gives description for item in CB table. 

---

I have tried correcting the issue the same way you just described, with the same results.

If the components are linked, that part is still working and you don't need to do it again. What you can do is Edit Component on the panel footprint and click Catalog Lookup, and choose the part again. After you have done that, it will continue looking at the correct catalog table going forward. Once you've fixed it, it will stick. Unfortunately that's a pain.

If your catalog numbers are linked up with footprints in the Footprint Database, it might be faster to delete all the footprints and reinsert them using Schematic List.

[rhesusminus · Accepted solution]

Just a little FYI.

You should not merge using Access. The Migration Tool inside AcadE will perfectly merge two databases. You'll find this tool on the Project-tab

[jallenDBQ7U]

That method appears to be the only way to solve it unless I want to do copy and paste in Excel.

What I find as interesting is that if I delete the component on the schematic drawing and recreate it, I still get no triggered update request for the panel even though surfer shows both locations.  The description on the panel component also still ends up blank (I suppose because the component number did not change).  Reselecting the schematic item for the panel item in the schematic list is still blank for description.

[alds02]

Do your panel footprints have FAMILY attributes?

What was your original workflow? Panel first then schematics, or other way? What method did you *originally* use to associate the components? It would be nice to come to some conclusions about the most robust way to get this done.

[jallenDBQ7U]

If I right click on any of my panel components and select List/Edit Attributes it does have this for most of them.  There are exceptions like Duct, Din Rail, etc. Some of the components I created, but most are from older projects

As we are finding out now, it must not matter if FAMILY is provided for footprints even though Symbol Editor lists it as a required attribute.  When I create any symbol I usually just copy and paste a group of attributes from a template drawing and edit the values.

We have a mixture of situations.  We make copies of similar projects and modify them for new ones.  This means it brings along a panel layout with the schematics.  We also have scenarios where the customer has not given us all of their information when the project first starts.