Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Desired custom field in Purchase Information, since API search is not working in our case #889

Open
balbet opened this issue Mar 10, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@balbet
Copy link

balbet commented Mar 10, 2025

Is your feature request related to a problem? Please describe.

We started using part-DB and it's a great solution! But we are finding some difficulties. The approach our company chose was to use components with alternatives. This way, we create a part-dB component with Manufacturer Part Number = "CRCW08050000Z0E**", where the "**" means that any component matching this pattern is valid to be used. We can't change this value, because it must match our Altium database name.

The problem arises when we add the Purchase Information. Following with the given resistor example, we added it as:
Supplier="Digikey"
Supplier Part Number="541-4125-1-ND"
Link To Offer="https://www.digikey.es/en/products/detail/vishay-dale/CRCW08050000Z0EAC/7928547?s=N4IgTCBcDaIMICU4HUAMAOVBWVvUC1UBRAQThAF0BfIA"

As you can see, we would need another field with the MPN in the Purchase Information, which in this case would be "CRCW08050000Z0EAC" so that the last 2 characters could be different, always that it matches the pattern with the last "**".

Given the previous case, I can find the component linked to the order ID in this way:
https://our-part-db/api/orderdetails?supplierpartnr=541-4125-1-ND

Despite this, since we don't have that other MPN field available, we tried to add that extra information to the Supplier Part Number using this pattern:
Supplier Part Number="541-4125-1-ND << CRCW08050000Z0EAC >>"

But now the problem is that I can't find the component using the previous query, since the "supplierpartnr" doesn't exactly match. I can find it using the "Search" box using the web instead of the API, though.

I wonder which is the best solution you think it's better we apply here.

Describe the solution you'd like
Maybe there's already a way, but we couldn't find the way to add a custom field to the Purchase Information.

@balbet balbet added the enhancement New feature or request label Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant