PLM 360 IdeaStation
Share your wish list directly with the Autodesk PLM 360 Development Team
New Idea
0 Kudos

More flexible revision pinning

Status: Implemented
by Valued Contributor sten on ‎10-27-2014 08:36 AM

Please consider adding a way to pin the upcomming revision.


The need occurs when I have a Change Order where I am both releasing items and a BOM referencing those items.


 BOM unreleased -> A

      ITEM1   unrelease -> A

      ITEM2   unrelease -> A

      ASY      A -> B

           ITEM3 A -> B

           ITEM4 unrelease -> A


If I want to pin all revisions in this assembly I will have to create multiple hierachical Change Orders and release them one at the time.


I often want to pin revisions because the part revisions are not interchangeable, however having to do it hierachical makes it impractical.


Also, please consider adding scripting support for pinning.




Status: Implemented

Hi Sten,


I believe with the recent release, we have released a new feature that will be able to address and meet your request.


The new "Add Related BOM Items to Items on the Managed Iems Tab" will all users to add parents, direct children and all children to the managed Change Order.


Please check the Help Guide for additional information: What's New


thank you,






0 Kudos

SAML support for Single sign-on

Status: Implemented
by andy.matthews on ‎06-11-2014 02:22 AM

We have recently implemented Okta identity management ( and it has been very successful in not only helping to provision/deprovision access to our cloud apps centrally but has also helped drive adoption and usage of those apps.


Adding SAML 2.0 support to Autodesk PLM360 would be a huge boon. This would require users being able to sign in with a corporate email address which may or may not also be an Autodesk ID.

Status: Implemented
6 Kudos

I have several assemblies with 100+ unreleased sub-items. 


When I add them to a change order I have to find them at the top level and select them one at the time.


When I select the top level assembly I can see the subasseblies and items, but it does allow me to select them. I have to find them all at the top level.

Why not allow me to select items in a BOM tree?.





Status: Implemented

Hi Sten,


I am happy and excited regarding the new enhancement that will allow the users to Add Parent and Children items when adding items to the Change Order.


What's New: November 2014



2 Kudos

Debug mode

Status: Implemented
by keith.tyler on ‎06-27-2013 11:17 AM

It would be beneficial to have a debugging mode for scripting (including stepping through low level scripts for which code is not available).

Status: Implemented
Debugger was added to the May 2014 release! See Advanced Debugging in the Help at: ;
0 Kudos

Orphan Workflow State (bug)

Status: Implemented
by keith.tyler on ‎06-27-2013 08:50 AM


  • create a new workflow state
  • create a transition to the new workflow state
  • delete the transition to the workflow state
  • the workflow state disappears from the editor window
  • create a new workflow state with the same name
  • create a transition to the new workflow state
  • try to transition an object to the new workflow state
  • receive error "<new workflow state> is not the unique short name of a workflow step in the relevant workspace"

It appears the original workflow state was orphaned (still existed but unable to access in the workflow editor) when the transition to it was deleted.  The only workaround I could find was to delete the workspace and start over again.


Status: Implemented

Hi Keith,


We have fixed this issue and will be on the upcoming release - September 2014.


Thank you,




4 Kudos

​ Default filters in a picklist

Status: Implemented
by cruzj on ‎06-05-2013 10:43 AM
We would like to be able to narrow down a linked picklist for a certain criteria.

Example: We use Product ID as a unique identifier for products. In other workflows, we will link a picklist of Product IDs to a form so that we can assign more attributes to the product. Product ID  can have a status of "Assigned," "Orderable" or "Retired." We would like to pre-filter a picklist of products to show only those that are in status "Assigned" but not "Orderable" state. There is no current client-side scripting available today.

Only possible by "chaining" workspaces. Create a new picklist when the item changes status, e.g., when a Product ID is first released, spawn record in another workspace with the narrowed-down population of "Assigned." .

Status: Implemented
3 Kudos
Conditional form-building in a workspace with workflow. We would like to be able to change a form layout based on a classification. Classification is the capability where we get different fields in a form for different scenarios, for example, in pricing.

The pricing attributes necessary for a product for a price list effective period can change depending on the period or type of product. The actual pricing framework and calculation can change as frequently as every month or any ad hoc period as set by the pricing team.
Framework impacts to forms
Ex) We work on about price list effective periods at the same time – the form would be different for a different pricing framework

Per Jared: This is not on the roadmap. The team needs to talk to he product manager responsible for classifications for the expected timeline.
The workaround is that we would use a more complex form that needs to accommodate the superset of everything that might be needed. The workaround is not ideal.
Status: Implemented

Hi There,


We now have a technical preview availble for classification functionality in PLM 360. If you are interested to participate in this technical preview, please contact me directly at



0 Kudos

Udate all records vis import tool

Status: Implemented
by rjohnson on ‎05-24-2013 04:45 PM

SOmetimes you want to add a new field or change an existing field for all the records in a WS.  If there are hundreds of records, this is a tedious task.  It would be great to be able to run a report to export the desired records to Excel.  Then you can easily edit the Excel file to add or chnage the fields.  Finally, you would import this Excel file and update the WS.  Currently, the import won't work if the record exists so you have to purge the WS and import to create new records.  This is not ideal if you have other workspaces and records linked to the records you need to update.


I'd like to see the ability in the import tool to check a box to check if a record already exists, then just update it.

Status: Implemented

Hi rjonhson,


Currently with our importing tool, you can add new records and add new fields to existing records.


Please visit our Help Guide for additional informaiton - Help Guide



1 Kudo

Create Views

Status: Implemented
by Contributor bverboort on ‎05-23-2013 02:56 PM

Allow user created views to be global for other tennant members to leverage (Admin controlled)

Status: Implemented
1 Kudo

Pre-Filtering a Linked Pick List

Status: Implemented
by Contributor zep.tyrushudson on ‎05-06-2013 11:28 AM


I think it would be very useful to be able to "pre-filter" a pick list or linked pick list, using a pre-filtering text field, which can be editable, visible, or hidden.  For example, I have a linked pick list in a "Product Family" workspace that points to my Items and BOMs workspace.  I want users to be able to select one or more records from the Items and BOMs workspace, but I want them limited to a particular prefix (for example, we use 850- prefix for our SKU's).  In my Product Family items and details tab, I could create a hidden field with the text, "850", which could be used to pre-filter the linked pick list to only show items starting with "850".  When setting up the pre-filtering rules, it would be important to be able to specify the filter condition...starts with, contains, does not contain, etc.



Status: Implemented
Submit Your Ideas

Share and shape product ideas.

New Idea
You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register