New Features and Updates:

• UI/UX Enhancements. 

  • Users can now scroll through line items in the release modal with their mouse wheel, without having to hover over the scroll bar.

  • Change Order input fields have been removed for Solidworks PDM users and collapsed for Standard users when the “Create Release” box isn’t marked.

  • Removed “Update” button from settings modal

• Improved Validation speed for Solidworks PDM Professional. The validations applied for SolidWorks PDM in the manage parts modal have been optimized to improve efficiency and responsiveness. 

• PDM One Check-in auto-saving. When using PDM One’s check-in feature, any unsaved files are now saved before being closed and re-opened. 

Bug fixes:

• Refined “Get Latest” Warning Pop-ups. This update will prevent excessive warning pop-ups some users have experienced. Additionally, the detection logic has been updated to resolve an issue that caused the “local files are out of date” pop-up to appear too frequently.

• Duplicate Model Openings. Resolved an issue where multiple models could be opened simultaneously, causing validation problems.

• Files becoming unlinked after pull part. Resolved an issue where trailing white space on the component name was causing the plugin to disassociate CAD files from their associated Duro component. 

• SolidWorks PDM Professional exception on switching files. Resolved a null reference exception that was occurring when switching files.

• Deleting Rows from Grids. Resolved a bug that allowed users to delete rows from the grids in the plugin by pressing the delete key. 

• Exception on PDM One check-in. Resolved an exception that was occurring on PDM One check-in.

New Features and Updates:

• UI/UX Enhancements

  • Users can now scroll through line items in the release modal with their mouse wheel, without having to hover over the scroll bar.

  • Collapsed Change Order input fields in release modal when the “Create Release” box isn’t marked.

  • Removed “Update” button from settings modal.

Bug fixes:

• Refined “Get Latest” Warning Pop-ups. This update will prevent excessive warning pop-ups some users have experienced. Additionally, the detection logic has been updated to resolve an issue that caused the “local files are out of date” pop-up to appear too frequently.

• PDM One Check in auto-saving. When using PDM One’s check in feature, any unsaved files are now saved prior to being closed and re-opened.

This release improves workflow accuracy, reduces manual documentation effort, and ensures better synchronization between SolidWorks PDM Pro and Duro.

New Features and Updates:

• The ability to save design updates and supporting documentation is now available for all SolidWorks users.

• Auto-creation of supporting documentation on Change Orders has been improved.

• The Duro Revision SolidWorks property now more closely aligns with Duro PLM updates.

• SolidWorks files linked to Duro components can now be renamed.

  • There is a known issue with duplicate file names partially saving and disabling the SWX component link. A fix is currently in the works.

• Improved log file reporting for diagnostics.

• UI/UX improvements.

New Features and Updates:

• UI/UX improvements.

This update delivers a more stable and reliable syncing process between Duro and Onshape, ensuring the correct release version is always reflected in Duro. It strengthens the digital thread, providing a trustworthy historical record of every release.

These improvements make the integration more dependable than ever, eliminating historical sync issues and ensuring a consistently stable connection.

New Features and Updates:

• Admins can now reset webhooks directly, eliminating the need to contact Duro when sync issues arise. This reduces downtime and keeps your workflow moving.

• Clearer webhook status updates. Users can now see clear communication of webhook connection status, making it easier to catch and resolve sync issues.

• Improved sync feedback UI. We’ve enhanced the interface so users can clearly see when a sync is in progress or completed.

Bug fixes:

• An issue preventing the manual addition of certain component types (Fuse, LED, Wire, Standoff, Nut, and Miscellaneous Mechanical) has been resolved.

Welcome to our first changelog of 2025! Our developers have been hard at work behind the scenes to enhance your experience with Duro, so this round-up is a bit longer than usual. To make things easier to navigate, we’ve organized everything into categories so you can quickly find what’s most relevant to you.

New Features and Updates:

• Change Order updates:

  • Isolate 'Draft' Change Orders: Users can now focus specifically on change orders in the draft stage, which are editable but not yet submitted for approval.

  • Filter by Change Order Type: Users can now filter change orders by type—DCO (Documentation Change Orders), ECO (Engineering Change Orders), or MCO (Manufacturing Change Orders).

• Character limits on Change Order descriptions have been significantly increased so that they can comprehensively describe all changes and reasoning in large COs.

• Configurations Tab is now a default setting for all accounts, allowing users to manage several account settings. 

• Filters now persist across pages and edits. Applied filters stay active when navigating pages, and modified components remain visible until the filter is updated.

• UI/UX improvements.

Bug fixes:

• A bug was fixed to ensure that the "author" of listed changes on a Change Order is correctly tied to the ECO Submitter, rather than the final approver.

• When a Change Order is rejected, components are now editable so users can fix the errors and resubmit the same Change Order.

• Approval Type is now locked for Change Orders with mandatory templates.

• Filter labels have been clarified to better describe validation statuses.

• Fixes made to the "Multiple ECOs" validation rule.

Bug fixes - Change Orders via ERP webhook:

• Default date issue resolved.

• Validation has been added to the date fields.

• The “item type” dropdown has been updated to match the options in the old Change Order system.

• “Start date” and “item type” now correctly appear in the component tile after approval.

New Features and Updates:

• PDM One: Documents are no longer defaulting to being generated on check-in. Users can select whether to generate documents on each check-in

Bug Fixes:

• PDM One: Some configurations still permitted editing of CAD files even when not checked-out (i.e. locked)

New Features and Updates:

• PDM One: Documents are no longer defaulting to being generated on check-in. Users can select whether to generate documents on each check-in

Bug Fixes:

• PDM One: Some configurations still permitted editing of CAD files even when not checked-out (i.e. locked)

Bug Fixes:

• All nested level child data is now being mapped over from NX when part numbers are pulled.

Bug Fixes:

• All nested level child data is now being mapped over from NX when part numbers are pulled.

New Features and Updates:

• Now, in addition to Box.com, Dropbox, and Google Drive, customers can choose to host their CAD files on Duro's servers for PDM! No 3rd party account needed

• General UI cleanup

Bug Fixes:

• Fixed issue when multiple CAD files are open unsaved changes can be lost when a ECO is approved

New Features and Updates:

• Now, in addition to Box.com, Dropbox, and Google Drive, customers can choose to host their CAD files on Duro's servers for PDM! No 3rd party account needed

• General UI cleanup

Bug Fixes:

• Fixed issue when multiple CAD files are open unsaved changes can be lost when a ECO is approved

Known Issues:

• Material specification is being added to all components released

New Features and Updates:

• Support for Solidworks PDM Standard added

• Automatically save latest changes to server when checking-in CAD files in PDM

• Automatically check for latest revisions when opening CAD files locally

• General UI cleanup and improvements

Bug Fixes:

• Mass value now properly updates from CAD to Duro web client

• Revision value now matches in web client to CAD plugin

New Features and Updates:

• Added "Save" workflow to the Release Modal, so now users can make incremental saves from CAD to Duro, without requiring an ECO

• Added custom fields mapping from CAD to Duro

Bug Fixes:

• General UI/UX polish

New Features and Updates:

• Added "Save" workflow to the Release Modal, so now users can make incremental saves from CAD to Duro, without requiring an ECO

• Added custom fields mapping from CAD to Duro

Bug Fixes:

• General UI/UX polish

Bug Fix:

• Resolved error message on Saving files multiple times

Bug Fix:

• Fixed issue where unsupported configurations casued NX to crash.

Bug Fixes: 

• Fixed Manual Linking to properly display all fields in Manage Parts Modal

• Fixed automatic state transitions crashing Solidworks for assemblies.

• Fixed assemblies and their associated drawings not updating automatically after a Change Order is approved or rejected in the Duro web client. 

• General UI fixes

Known Issues: 

• Not all documents are updated after a Change Order is Rejected and Re-submitted

Bug Fixes: 

• Fixed Manual Linking to properly display all fields in Manage Parts Modal

• Fixed automatic state transitions crashing NX for assemblies.

• Fixed assemblies and their associated drawings not updating automatically after a Change Order is approved or rejected in the Duro web client. 

• General UI fixes

Known Issues: 

• Not all documents are updated after a Change Order is Rejected and Re-submitted

New Features and Updates:

• Updated Renaming PDM files to retain file history in PDM

• Allowed for Electrical Categories to show in Manage Parts modal.

• General UI fixes

New Features and Updates:

• Allowed for Electrical Categories to show in Manage Parts modal.

• General UI fixes

New Features and Updates:

• Revision values properly update on the Release workflow

• Disabled New Family and Free From CPN Creation for 2-variable CPN schemes

• Allow for recursive releasing for components in folders.

• PDM One Admin Check-in

• Fixed BOM and Documents being overwritten.

• Fixed BOM Quantities having correct values.

• User interface cleanup and stability improvements

Known Issues: 

• Pull Part Number on the Manage Parts modal may fail with no error message. It is recommended to restart Solidworks if this occurs.

New Features and Updates:

• Revision values properly update on the Release workflow

• Disabled New Family and Free From CPN Creation for 2-variable CPN schemes

• Allow for recursive releasing for components in folders.

• PDM One Admin Check-in

• Fixed BOM and Documents being overwritten.

• Fixed BOM Quantities having correct values.

• User interface cleanup and stability improvements

Known Issues: 

• Pull Part Number on the Manage Parts modal may fail with no error message. It is recommended to restart NX if this occurs.

Re-imagined, revitalized, and rebuilt from the ground up, today we are releasing our brand-new Solidworks 2.0 plugin!

In this release we've focused our efforts on quality (stability), performance (speed), and consistency across all our available CAD plugins (including our newly released NX plugin — more to come on that shortly).

From day one we've wanted to create an embedded experience with our PLM product, including the ability to pull part, link, and release to your main library. To date, this experience has sufficed, however over the years the plugin performance has slowed, and tech debt has halted our ability to innovate, disallowing us from building new features confidently without sacrificing existing functionality.

With our new internal SDK architecture, we are now incredibly excited to showcase not only a more performant and feature-parity plugin but a slew of new features showcasing a first-class experience. This architectural overhaul is a testament to our commitment to delivering top-tier solutions that meet the evolving needs of our users.

Some of the key highlights of the Solidworks 2.0 plugin include:

We believe that this release marks a significant milestone in our journey to become the market leader in PLM solutions with an ever-expanding tech stack. Our dedication to enhancing customer experiences is evident in every line of code, every new feature, and every performance improvement. We are confident that the Solidworks 2.0 plugin will not only meet but exceed your expectations, providing a robust and innovative tool that empowers you to achieve more.

Stay tuned for more [frequent] updates and detailed walkthroughs on how to make the most of the new features in the Solidworks 2.0 plugin. Thank you for your continued support and trust in Duro!

We are thrilled to announce that Duro is now officially listed in the Prismatic Marketplace. This milestone marks a significant step forward for our platform, providing us with wider visibility and access to new markets. It underscores our strategic positioning as a robust platform with an expansive and extendable tech stack.

Prismatic, an industry-leading iPaaS (Integration Platform as a Service), powers many of the Duro extensions we use internally. With our listing in the public marketplace, developers can now leverage Prismatic’s low/no-code platform to build their own integrations with Duro in a matter of minutes.

Leveraging the simple to digest Duro Connector Docs, Developers and non-developers alike can now quickly create custom integrations using Prismatic's easy to use Integration Designer tools, enhancing the functionality and versatility of the Duro platform. With this strengthened ecosystem, we are excited about the opportunities this listing presents and look forward to seeing the innovative integrations our community will create.

If you have any questions or need assistance getting started, our support team is here to help.

We are thrilled to announce the latest addition to our available backup solutions within our Prismatic tech stack: Microsoft OneDrive. This new integration offers a robust backup utility for your component assemblies, sourcing information, custom specifications, and associated documents. With just a 30-second plug-and-play configuration, you can seamlessly integrate OneDrive into your workflow, ensuring your critical data is securely backed up on autopilot.

Our commitment to expanding the Duro integration ecosystem continues, providing you with the tools you need to enhance your productivity and streamline your processes. If you need assistance with setup, our support team is ready to help. Don’t hesitate to reach out!

Thanks to a comprehensive upgrade of our core object-relational mapper, we have achieved a remarkable 5x increase in response performance across all major API queries. This includes, but is not limited to, products, components, revision history, documents, change orders, and more.

Our internal benchmarks show that these improvements substantially and noticeably enhance the user experience, providing a smoother and faster flow within our web application. This upgrade underscores our commitment to delivering top-notch performance and a seamless user experience for all Duro PLM platform users. Stay tuned for more updates and thank you for your continued support!

Bug fixes & Enhancements

• Create & Update Component Mutation now available in graphql preview gateway

  • available at mfg.duro.app/graphql/preview

Now available in Duro — The Nexar API provides real-time supply chain visibility and insights for your bill of materials. Duro incorporates MPN/DPN search and directly integrates pricing and availability data into your system.

Bug Fixes

• Onshape <--> Duro property syncronization

• [API] Add flag to cpn document when creating a free-form override cpn

• File import creates component that does not have a cpn

More improvements & fixes

• Component create & update GraphQL mutations for the upcoming API Gateway

• Change Order UI Overhaul private beta opt-in experience

Beta preview access for our latest integration is now available. This feature allows you to automatically back up your Duro component library to a designated folder in your Google Drive Workspace account on a weekly schedule. This integration not only ensures that your critical data is securely stored and easily recoverable, but it also enhances collaboration by allowing your team to access the latest backups directly from Google Drive. With this seamless integration, you can rest assured that your component library is always up-to-date and protected against data loss, helping streamline your workflow and boost productivity.

Reach out to us if you're interested in beta access.

Duro's integration with Jira streamlines project management by automatically generating a corresponding Jira ticket each time a Change Order is created in Duro. This integration saves significant time and eliminates the hassle of (1) creating a ticket in Jira and (2) manually matching ticket titles to Change Order IDs, ensuring immediate connectivity between the two platforms. Users benefit from this direct link as it keeps teams aligned and projects moving forward.

Setting up this integration is straightforward and requires no coding, making it accessible for all technical levels. With just a few clicks, you can activate this feature, allowing you to focus more on project execution and less on administrative tasks.

Learn more about the Duro|Jira integration in our help center.

Improvements & Fixes

• Updated NetSuite ERP options for webhooks that allow including children in payload without adding child components to a ChangeOrder

• Add select all option in the checkbox for all assemblies

• Add Custom Fields/Specs to Import, Export and Search

• Include FT in package type enum

PLM 3.24.0

• Optimized API (/graphql), caching components requests on API layer

More improvements & fixes

• Make account config custom action available for workflows in other repos

• Account creation & config action should support staging envs

• Remove Duplicate Parts in Grid View

• Implement the search functionality on the tree and grid view in Solidworks

PLM 3.24.1

• ChangeOrderEdit: ERP / Edit Form Components

• Create validation state and reducers

It's been a busy holly jolly holiday season at Duro as we sprint to the end of the year pushing out bug fixes, performance enhancements, and UI polish. Also, welcome to our new changelog! We'll be putting our release notes here going forward into the new year. Cheers from the Duro factory floor!

Feature Enhancements

• Modify createComponent GraphQL API operation for SpaceX scheme

• Custom Fields/Specs are now available to Import, Export and Search

• UI/UX sweep, better icons, consistent graphics used across Duro web application

• New GraphQL mutation to update CAD settings

• Add prototype and production status in Change Orders

Bug Fixes

• PLM: Fix missing delete icon for Documents

• Solidworks: Fix files not opening when UserById returns null for CAD parameters

• Solidworks: Fix occasional blank screen after logging in

• API: Fix setting assemblyRevisionId and componentId in children

Security

• SEV 1 fix for Arbitrary File Download + Directory Traversal (Read Access)

• Better integration with the SWX Plugin

• Improved backend performance for Product and Component library pages, making it faster to load the second page and beyond in companies with large libraries.

• Improved trimming of spaces around strings when editing components and products.

• Fixed a number of bugs in the backend

• GraphQL mutation to Update CAD Settings of Active Library

• Connect SWX Custom Properties

• Fix SWX rename failing to load in Duro Web App

• Fix SWX PDM for assemblies and drawing files

• SWX drawing conversion/export only resulting in 1 sheet of multi-sheet drawing

• Duro now recognizes components made from Save As in SWX

• Prototype status enabled in SWX plugin

• CPN SWX file name not syncing to Duro component

• Fix SWX some users having issues sign-in

• SWX 2.19 not allowing re-link Duro to SWX

• Unable to create components through import from file when Custom specs are included for Riedel

• Kodiak - Incorrect Revision Scheme in V3.1 release

• GraphQL mutation to Update CAD Settings of Active Library

• Drata | Web Application Firewall in Place

• Unable to bulk update child components data through parent component

• SoundBoks - Can't pull part numbers in Onshape (copy)

• GraphQL query for CAD Settings of Active Library

New Features

• Duro PDMone Initial Release

Bug Fixes

• Single Part Not Showing in Part Card after Pull Part Dialog Closed

• Remove call to clear cookies when closing Solidworks.

Enhancements

• Disable Popup Asking if Users if They Want to automatically Create Change Order using Solidworks PDM workflows.

Enhancements

• Re-enable "Prototype" Status for PDM users

• Display descriptive release errors if a release is not allowed

Bug Fixes

• Unlinked item from SWX still passing metadata to Duro

• SWX Plug In Does not always recognize existing components CPN

• Solidworks plugin inconsistently loads data/doesn't show

• Incorrect Alert Messages when Adding a Part in Solidworks

Bug Fixes

• Fix crash for non-PDM machines on startup.

New Features

• Solidworks PDM State Changes Automatically Create Change Orders

Enhancements

• Increase API Call Timeout to 30 Seconds

Bug Fixes

• Deleted ECOs Should Not Block New ECO Creation

• CPN SWX file name not syncing to Duro component

• Some customers were unable to install 3.02

• Sometimes no categories appeared for Solidworks components

• SWX part card revision updating prematurely

• Update Suppressed Components in Parent Assembly

• Files continually unlinked after resyncing.

• GraphQL API Improvements

  • Added Apollo Federation at a new endpoint based on the web URL.

    • Example, with the web url https://mfg.duro.app the GraphQl url will be https://mfg.duro.app/graphql.

  • Fixed issued with the Prouct and Component mutations.

  • Improved permissions checkes.

  • Fixed variant group creation.

  • Fixed how the modified field in handled for Products and Components.

  • Add solidWorksAnalytics to user resolver

• Web Client Improvements

  • Fixed issues with Component view and edit pages

    • The different tab properly display information when moving betweent them.

    • Fixed issues with the error could display being wrong.

• Make UoM Case Insensitive

• SWX Must Update may not be working

• File release measurement error

• Issues with SWX Configuration files being recognized in plug in correctly

• SWX Plug in overwrite existing loaded item

• Duro does not recognize component made from Save As in SWX

• SWX analytics values appear off

• Match Component by CPN filename