- Collapse View
- Expand View
- Mark all as New
- Mark all as Read
- Float this IdeaStation to the Top
- Subscribe
- Bookmark
- Subscribe to RSS Feed
- Invite a Friend
At this time, all views are by individual. There is not a way to globally configure a view globally. Item Views should be able to be modified for an entire team from the system admin rather than from case to case basis.
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.
I ask to introduce the ability to show the relationship graph attached this post with custom icons.
The graph would be much more clear if I could link the icon to an image filed of the record.
Just two use cases as example:
1) BOM VISUALIZATION: Quickly view the components types in a BOM visualization.
2) FASHION application: Showing a dress component list I could show a tissue sample image.
But applications are many...
Thanks and best regards,
Andrea Capuzzo
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.
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()
It is common for a BOM to have a wide variety of components/items associated in it (For Example Screws, Washers, Nuts, Hardware, Motors and sub-assemblies). Many would organize those components/items in more than one workspace within PLM360.
In order to mass create/update BOMs of a specific product practically, the import tool must allow access to add/remove 'child' items from other workspaces - Especially if PLM360 allows you to do it manually.
Having access to only the 'Parent' workspace in the import tool is impractical. This either results in poor item organization within the workspace when trying to make the import tool work OR results the user performing a tedious manual process.
Overall, I think the import tool is a great feature for BOMs; however it still needs to incorporate a multi-workspace functionality to serve its purpose practically.
Regards,
Amrit Singh
Please create ability to add BOM tab field details here, so data can be added in a single step instead of multiple.
It would be a nice feature to set a specific field that can only be accessed by specific groups and restrict other groups from seeing this field. e.g. Cost
Allowing external suppliers access to Items/BOMs but not seeing the Cost Field
-
Applications
-
Bill of Materials
-
Dashboard
We should be able to add Item Detail fields to the BOM tab. I would love to see that functionality soon.
Inventor Fusion mutates to Fusion360, a cloud based application, as it looks like. I've started using the beta of Fusion360. Descriptions of models created in Fusion360 appear in PLM360 - great. I'm on OSX wherever possible and do highly welcome the availability of Fusion360 for Mac.
I'd expect that PLM360 starts Fusion360 (if it's a Fusion file) when I click a link at the info of a part in the BOM of PLM360. I'm sure that there will be more cloud based apps and it should be standard, that a model or a design for which there is an entry in PLM360 can be opened directly from the PLM360 UI.
Privilege levels should be granted to memebers of the team - not everybody should be authorized to change.
Wolf Ehrke
