Skip to main content
This page was auto-migrated from the legacy ION manual. Some images and cross-links may need follow-up cleanup. Original: _legacy-export/integrations/duro.md.
Skip to the Set Up below for instructions on how to deploy or reconfigure this integration. Establish Duro as the source of truth for product/component metadata, and bill of materials (BOM), while ION parts remain up to date with changes made in Duro with no manual intervention. This integration eliminates the extra effort it typically takes to manually import part details and BOM information into ION, which will help you create procedures and get to building faster. https://www.loom.com/share/3d3d6732c5f648688179e797aa7c7621?sid=748a2559-f090-4afd-bcda-8d13e50425a2

​
Duro Change Order Approved

On change order approval within Duro, an integration with ION will fire which propagates part information and BOM changes to ION. Any time a new part, a new revision, or a new BOM is released in Duro via the change order process, that information will propagate to ION. ION, with the use of mbom-versions.md, automatically generates a new draft mBOM version for that part, adds all of the components, and then releases that mBOM version in ION.
Remember, ION does not have a release process and we do not prevent you from manipulating part data in ION once a component has been released in Duro. This is useful for setting sourcing strategy, tracking type, and supplier part relationships in ION if it is not set in Duro. If you want to prevent this, see role-based-access-control.

​
mBOMs Versions in ION

We recommend that you create a new mBOM version that you release in ION if you want to add additional information such as tape, epoxies, and adhesives not covered by the engineering BOM.

​
Determining the Suppliers of your BOM

When importing your BOM, we recommend you use supplier part numbers to map the BOM to specific suppliers. This data feeds autoplan-suggested-suppliers-and-procedures.mdand often your procurement team lives in ION, so we do not recommend setting up the integration to pull this data from Duro and instead create that data directly in ION. We recommend creating a DCO to release a BOM into ION before it gets approved via an ECO, so you can parallelize sourcing and finalizing the engineering instead of treating this as a waterfall approach. The sole caveat is that you may want manufacturers and MPNs to come over to ION because engineering often is pulling those parts from a specific spec and manufacturer, especially for commercially available parts. From there, the sourcing team can use ION to determine the supplier/distributor for those parts.

​
Set up

  1. Navigate to the Integrations page designated by the two arrows in the bottom left corner of your screen.
  2. Select Duro integration instance from the marketplace, and hit Configure.
  3. Hit Next and add your API credentials. You can find documentation on API credentials here api-keys.md
    • IMPORTANT: Each API Key is associated with a specific environment, be sure to generate the API keys from the correct environment and configure the automation to the designated environment. Be sure to also select the correct environment. If you are on the Gov Cloud environment then selecting Production will result in an error. Contact your Customer Success Engineer if you are unsure which environment you are on.
  4. Generate a Duro API Key by navigating to the integration settings page and select Get API Key. Input that into the configuration of the integration.
    1. NOTE: Duro API keys expire every 90 days. Learn more from Duro here!
  5. Select the Duro GraphQL Link. There are two possible values. ITAR clients should use https://app.goveduro.us/graphql while all others should use https://mfg-core-api.duro.app/graphql
  6. Ensure the revision schemes for your production and prototype parts are created in ION and the names inputted into the configuration screen. Ensure the allow overflow box is checked if you are going to go over two characters.
  7. To finish the configuration, you can map the data between the two platforms by adding key value pairs for ION native attributes and custom attributes. The keys are ION fields and the values are Duro fields. Below is an example of the mapping. 1.
  8. You can map values from the primary source as well such as manufacturer or distributor, however, please see the above section on Suppliers in ION for our recommended approach.
  9. Hit Finish to complete the integration configuration. Head to the Test page, and copy the Post URL of Flow 1 by clicking the clipboard icon as seen below in order to configure the webhook in Duro in the following step.
  10. The last step is creating a Duro webhook that sends data to ION when a change order is approved. Navigate to the webhook page in settings and create new one. You can populate the URL with the URL you captured in the previous step. Fill out the remaining details as seen below.
Please ensure the Include all Components and Products data below is checked as seen below

​
Current Limitations and Troubleshooting

  • At the moment, file attachments and links to specs, manufacturers, distributors, drawings, and others are not supported. Don’t hesitate to contact our team if this is a critical need for your operation.
  • Ensure your revision schemas are updated in ION to support Alphabetical and Numerical and ensure the integration settings reflect the case-sensitive names. If you change the schema names in ION, ensure the integration is updated to reflect that.
  • Ensure you have selected the correct Environment and Duro GraphQL Link
  • If your Duro integration was working then suddenly stops, check your Duro API keys. The API keys from Duro are unique to each user and expire every 90 days! Learn more from Duro here.