Component Review Issues
Worked for 1 min 21 sec
I thoroughly checked the current review output, schematic properties, BOM, layout nodes, and property definitions.
Findings:
- The warning is still exactly on Project, not on the three terminals.
- The terminals have:
- Part Type
- Designator Prefix
- Pin Number
- The BOM currently reports no parts added, which suggests this part-project’s metadata is not being surfaced as a normal BOM component.
- The recognized sourcing property names are:
- Manufacturer Part Number
- Manufacturer Name
- Datasheet URL
- The review message says “Datasheet is not set”, but “Datasheet” is not a recognized property name; the valid label is “Datasheet URL.”
So this looks like a review/check inconsistency or scoping bug: the checker reports missing project-level metadata, but the canonical property definitions expose those sourcing fields as component-level properties, and the review message uses “Datasheet” instead of the recognized “Datasheet URL.”
If you already see those fields filled at the project level in the UI, the likely causes are:
- The review is checking a different internal metadata object than the visible project properties.
- The field is named visually as “Datasheet,” but the checker expects canonical Datasheet URL /
datasheet_url. - The review result may be stale, but its timestamp shows it ran recently, so stale review is less likely.
- This specific generic part-project type may not be mapping project-level sourcing metadata into the component-review checker correctly.
Bottom line: your metadata may be present in the UI, but the checker is not recognizing it because of an internal scope/key mismatch.
Fix metadata keys
Document review bug
Check hidden fields
Verify part readiness
