• Industries
  • Products
  • Buy
  • Services & Support
  • Communities
  • Discussion Groups
    New Idea
    5 Kudos

    Allow bulk Import into Multiple Selection Picklists

    Status: Accepted
    by 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: Accepted
    6 Kudos

    Relationships Graph with custom images

    Status: Accepted
    by ACapuzzo on ‎10-11-2012 03:09 AM

    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

    Status: Accepted
    8 Kudos

    Scripting Access to Relationships Tab

    Status: Implemented
    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: Implemented
    4 Kudos

    Item Preview Enhancment

    Status: Accepted
    by 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: Accepted
    Great Idea, I've seen some mockups that are very similar to this idea!
    3 Kudos

    Scripting Access BOM & Sourcing Tab

    Status: Implemented
    by 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: Implemented

     

    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()

     

    2 Kudos

    Derived grid field values

    Status: Accepted
    by Distinguished Contributor dkeeley 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.

    Status: Accepted
    3 Kudos

    In the relationships tab, the cross-referenced items are listed under the column: Item, Current State, Type of Relationship, and Description. It would be nice to identify which workspaces the items are originated since the items might be cross-referenced from multiple workspaces.

     

    e.g. certain item in [WS]Products might be related to items from [WS]Tests and [WS]Calculations. It would be nice to identify the items are either from [WS]Tests or [WS]Calcuations by adding another column called Workspace or Category.

     

    Thanks,

    Frank

    Status: Accepted
    1 Kudo
    ScottMoyse

    Add Item Details on the BOM tab

    Status: Accepted
    by *Expert Elite* on ‎10-07-2012 01:29 PM

    We should be able to add Item Detail fields to the BOM tab. I would love to see that functionality soon.

    Status: Accepted
    I know this is part of the derived field’s strategy, we should see this functionality before long. - Jared
    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.
    0 Kudos
    obourne

    Spawning Links Should be Bidirectional

    Status: Implemented
    by Valued Contributor obourne ‎08-20-2012 03:27 PM - edited ‎08-20-2012 03:28 PM

    When an item is spawned by a workflow there is an option to link link to the spawned item to the "spawned by" item. There should be an option in the spawing item to automatically link to the item it spawned. I know this can be done with abit of scripting but I think it really should just be a check box/option.

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


    PLM 360 Survey