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