PLM 360 IdeaStation
Share your wish list directly with the Autodesk PLM 360 Development Team
New Idea
2 Kudos
When assigning Products to Release as a BOM, we see all Revisions of the Products in the revision control workspace. The tool seems to be smart and no matter which Rev you pick, when you look at the BOM as of a certain date, the right Rev is displayed. Is there a way to see Product without the Revs - last version only or name only? We would see Product#32 three times, for example, for sA, B, and C (future).
2 Kudos
cruzj

Increase​ Item descriptors

Status: Accepted
by cruzj on ‎06-04-2013 04:00 PM
When a user uses a filter, there are only 4 item descriptors available.
 
Key identifiers for product data take up at least 3 descriptors automatically 
1) Product ID
2) Product Name
3) Item status - represents different states of an item (e.g., Assigned, Orderable, Retired)

It would be useful to have additional descriptors in case addtional attributes are needed such as Release, Platform or Deployment, Effectivity dates, for example.
Status: Accepted
Hi cruzj, I'm not really understanding the use case for this request. Currently the descriptor pulls the information from fields in the Item Details. Some of our revision controllled workspace, have their own indicators, for Lifecylce, Revision Letter, Effective Date. The more you add to the descriptor, the longer the name of the record. Please help me understand the need for this request thank you, Trung
2 Kudos
We use BOMs to show data hierarchies.
Example hierarchy:
  • Pricing - which is a parent of
  • Offering - which is a parent of
  • Release - which is a parent of
  • Product Line Code - which is the lowest level of child
Can we do a validation from a field in a Parent item details form to a child BOM?
The Pricing form has a field to display Product name and show some derived fields that are used in a pricing calculations. Can we ensure that somewhere down the chain of BOMs, that the same Product is added as a child? 

The validation logic may possibly only be done on a workflow transition.


2 Kudos

Our team used BOMs to create data hierarchies.

For example, Pricing has a child Offering, which has a child Release, which has a child PLC (Product Line Code).

When a user selects a BOM in Pricing, can the user see the down the relationships to Offering, Release and PLC?

0 Kudos

The default text box in the initial view should be customizable or auto size to the text in it. I realize you can hover over it and see the fill value but it would be handy to see the whole thing to start

Status: Future Consideration
Thank you for submitting this request. We will add this to future enhancement list.
6 Kudos
DonovanJr

Scripting Access BOM & Sourcing Tab

Status: Duplicate
by Active Contributor DonovanJr on ‎12-03-2012 11:37 AM

We need access via the Server Side Sripting to both the BOM Tab & Sourcing Tab.

 

I believe there are several support threads as well as Ideastation references to this functionality but I felt we needed a clear Idea Post for this functionality.

 

Similar to the new object record item.workflowitems recently added we need to have information contained in the BOM & Sourcing tabs for use in scripting.

 

An example would be having an assembly shown on an Sakes Quote Grid and a workflow that would explode the BOM children of that assembly into the grid of an RFQ and access the default supplier to create a master RFQ for cloning quoting purposes.

 

Ideally this would be read/write access for back feed updating of costing etc.

 

Status: Duplicate

 

BOM Final implementation:

RELATED and QUANTITY are required, others are optional:
item.boms.addBOM({ RELATED: part1, QUANTITY: 1.2, CUSTOM_FIELDS: { FIELD: 'value' }, ITEM_NUMBER: 10, QUOTE: part1.sourcing[0].quote[1] })

First two arguments are required, others are optional:
item.boms.addBOM(part2, 2.3, { FIELD: 'value' }, 11, part2.sourcing[1].quote[2])

var bom = bom;

Can assign:
bom.item.ANY_CUSTOM_FIELD
bom.qty
bom.quantity - Synonym for bom.qty
bom.quote
bom.ANY_CUSTOM_FIELD

Can read:
bom.id
bom.item
bom.item.ANY_CUSTOM_FIELD
bom.itemNumber
bom.descriptor
bom.qty
bom.quantity - Synonym for bom.qty
bom.quote - See Sourcing Tab support for fields which can be read
bom.ANY_CUSTOM_FIELD

bom.remove()

NOTE: You can assign to quote, for example:
bom.quote = target.sourcing[0].quote[1];

However, you cannot change the quote through the BOM:
bom.quote.min = 10;
is not guaranteed to persist changes to the quote. To ensure that changes are persisted, change the quote via the sourcing:
target.sourcing[0].quote[1].min = 10;


Sourcing/Quote implementation:

SOURCING:

Everything but SUPPLIER is optional:
item.sourcing.addSourcing({ SUPPLIER: supplier1, SUPPLIER_PART_NUM: 'ABC-123', MANUFACTURER: 'Manufacturer Name', MANUFACTURER_PART_NUM: 'MAN-123', COMMENT: 'Comment', CUSTOM_FIELDS: { FIELD: 'value' } })

Everything but first argument is optional:
item.sourcing.addSourcing(supplier2, 'XYZ-789', 'Other Manufacturer', 'OTH-789', 'Comment', { FIELD: 'value' })

Can assign:
item.sourcing[0].supplier
item.sourcing[0].supplierPartNumber
item.sourcing[0].manufacturer
item.sourcing[0].manufacturerPartNumber
item.sourcing[0].comment
item.sourcing[0].ANY_CUSTOM_FIELD

Can read:
item.sourcing[0].supplier
item.sourcing[0].supplierPartNumber
item.sourcing[0].manufacturer
item.sourcing[0].manufacturerPartNumber
item.sourcing[0].comment
item.sourcing[0].quote
item.sourcing[0].quote.id to get quote ID
item.sourcing[0].ANY_CUSTOM_FIELD

item.sourcing[0].remove()

QUOTES:

Args are: min, max, leadTime, leadTimeType, unitCost, comment
leadTimeType can be 1, 7, 30, 365, 'Days', 'Weeks', 'Months', or 'Years':
item.sourcing[0].addQuote(100, 200, 12, 'Days', 12.34, 'Comment')

Can assign:
item.sourcing[0].quote[1].min
item.sourcing[0].quote[1].max
item.sourcing[0].quote[1].leadTime
item.sourcing[0].quote[1].leadTimeType - Can be values listed above
item.sourcing[0].quote[1].unitCost
item.sourcing[0].quote[1].comment
item.sourcing[0].quote[1].default - true or false

Can read:
item.sourcing[0].quote[1].id
item.sourcing[0].quote[1].min
item.sourcing[0].quote[1].max
item.sourcing[0].quote[1].leadTime
item.sourcing[0].quote[1].leadTimeType - Will give values above
item.sourcing[0].quote[1].unitCost
item.sourcing[0].quote[1].comment
item.sourcing[0].quote[1].default - true or false

item.sourcing[0].quote[1].remove()

 

5 Kudos
Asingh5

Allow bulk Import into Multiple Selection Picklists

Status: Duplicate
by Contributor Asingh5 ‎11-14-2012 10:52 AM - edited ‎11-14-2012 10:53 AM

When using the import tool, performing a bulk import of values into a "single selection" linking picklist is possible. Unfortunately I cannot select a "Multiple Selection" linking picklist it in my import to do the same thing.

 

This feature is very important for our company since it would allow us to show our linked product items in one specific field, as opposed to having multiple "single selection picklists"--which doesn’t make a clean visual. 

 

The data I have is in a excel format. With over thousands of entries, having the import tool to bulk import the linking picklist values in the multiple selection picklists would allow me to provide my tenant with the information it needs efficiently and visually appealing.

 

import.png

Status: Duplicate
Comma delimited values can now be imported into multi-select pick lists! See the PLM 360 "What's New in PLM 360" page for more details on the June 2013 release.
5 Kudos
Asingh5

Item Preview Enhancment

Status: Comments Requested
by Contributor Asingh5 ‎11-06-2012 08:22 AM - edited ‎11-06-2012 08:25 AM

The TABS section of the preview should open up and expand when clicked on instead of redirecting to the specific item. This would allow the quick easy access to key information such as BOM items, attachments, relationships, changes ext. Also there should be the ability to click the specified print view for the item as well.

 

Untitled.png

Status: Comments Requested
Great Idea, I've seen some mockups that are very similar to this idea!
3 Kudos
dkeeley

Derived grid field values

Status: Comments Requested
by Mentor on ‎10-31-2012 02:54 PM

Hi,

 

It would be useful to be able to create derived values on new items from grid field values on other items.

 

David.

0 Kudos

A Tenant may have 100-1000 buildings managed by a large property management group or builder etc.

 

Owner/Operator/Vendor groups to have access to View/create/update Accident/Service/Maintenance or other workspace requests and interact with Project schedules/tasks related to specific Buildings.

 

Owner/Operator/Vendor groups are linked to Buildings ( currently groups have access to roles which are linked to workspaces ) This feature is related to data within specific Facilities Management Workspaces.

 

Possible Solution

 

Configurable Picklist based on Owner/Operator/Vendor groups assigment to only present specific values e.g.Buildings

 

On Item creation, allow a script to add all Groups assigned to the Building which is required field to be added  as Additonal Owners

 

 

Status: Solution Provided
John, I think we'll cover this in the Divide tenant into "Project" areas ideaStation post. I think these issues are very similar, so let's consolidate them.
You are not logged in.

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

Announcements
IdeaStation Guidelines
Review guidelines and best practices
before posting a new idea


PLM 360 Survey