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.
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 ?
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." .
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.
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.
byAsingh511-14-201210:52 AM - edited 11-14-201210: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.
byAsingh511-06-201208:22 AM - edited 11-06-201208: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.
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.