New Idea
7 Kudos

If you could add the tabs to the workspace the same way you add a field, you would gain a ton of functionality. Even if you were still restricted to the same types of tabs currently available (grid, BOM, etc.), being able to add multiples of a tab and to add them only when necessary would be a great boost.

9 Kudos

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...

 

RelationshipGraph.JPG

Thanks and best regards,

Andrea Capuzzo

2 Kudos

Hi,

 

Today I came up against a mystery error because I had a derived field that was supposed to be set to derive from a multi-select picklist, but the source was blank When I tried to reset it, the field I wanted would not show on the list as I now realise you can't have a derived field that could show more than one value (i.e. coming from a multi-select picklist).

 

Could you add this functionality if it is possible as that would be v useful to ensure data only has to be changed in one place, yet is consistent throughout the system ?

 

Many thanks,

 

Fiona

4 Kudos
cruzj

​ Default filters in a picklist

Status: Duplicate
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: Duplicate
9 Kudos
pmaxted1

Scripting Access to Relationships Tab

Status: Duplicate
by pmaxted1 ‎08-02-2012 12:23 PM - edited ‎08-02-2012 12:25 PM

It is often both difficult and tedious to manually create relationships between different workspace items (as the picture below illustrates). It would save a lot of time to be able to write scripts to automatically add relationships between workspace items. 

 

Even tying the ability to add relationships into the function createItem('WS_WORKSPACE_ID') would be a huge time saver.

 

 

 

Item Relationships

Status: Duplicate
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!
1 Kudo
dsl145

Static BOM import from separate workspace

Status: Accepted
by dsl145 on ‎11-14-2013 09:23 AM

I've got a situation where we have imported a large amount of Heirarchy items from Autodesk Vault and we need to link a an assembly of items to a specific repair.

If we were able to import a static snap shot of the assembly of items and then be able to assign a QTY New to some of the items.

Status: Accepted
Hi DSL145, I'm not understand your request. Please elaborate and provide additional information. thanks, Trung
2 Kudos
We use product descriptors to select the correct record using filtered picklists. If the downstream data changes, the filtered picklist in another workspace does not update. For example, for a Product Release, there are two descriptors - name and year. The release is used in an offering that can have 3 states - Started, Active, Frozen. The name can change over time. If the name is changed in the original Product Name workspace, the changed name does not appear in the Product Release pick list that has the descriptors Name, Year.
There are some instances where we would like the descriptor not to change, for example, when the status of the offering is Frozen, we would like to see the descriptors at the time when the product was active. If the Offering is in Started status, the descriptors in the Product Release should update to the current values.

Note: Per Jared, currently under development.
Status: Future Consideration
This is an interesting request. It looks like you have communicated with Jared. We will add this to our future enhancement list, and connect with Jared.

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