I'd like to use Sharepoint to maintain UAT test results from different testers. I have a number of test cases, currently defined in a sharepoint list, categorized by 2 columns (Category level 1, Category level 2). I use these 2 columns as the two group by filters to users can easily navigate and find their use case. Now I' like to be able to store multiple results for each test case from multiple users. One idea is to create another list containing only the search results and to link the two columns to the other list of defined test cases.
You can have a "Results" list with a lookup column to the "Test Cases" list. That's generally how many-to-one relationships are handled in SharePoint.
Related
I am currently trying to display some manager/employee names based on business unit.
Each Business Unit could have multiple managers and multiple employees.
My question is can VLookup or any other method return a drop down list to select a certain manager/employee based on the Business unit selected?
Please see image below to see the layout and expected output.
I am hoping to use 3 drop down menus which when the business unit is selected to be able to auto populate first employee and manager in the list but also be able to have drop down menu for both to select other employees/managers etc.
Thank you.
screenshots
screenshots
screenshots
Please find my Excel-sheet in which I modulated a possible solution via the following link (shared on OneDrive):
https://cronos-my.sharepoint.com/:f:/g/personal/oortsja_cronos_be/EuUIF6pW95xGtcA0gQjwtIkB_x4LCc8oWks9VwoVTfrhJA?e=7fO6Dz
To summarize how I got to this solution:
I made different tables based on the data you provided (Business Unit > Manager > Employee). Using Name manager (see example), I gave those tables specific names that relate to their respective Business Unit > Manager > Employee.
Using =INDIRECT(), I reference those tables based on the names I gave them. E.g. table Ireland (Business Unit) contains values "John" and "Keith". Based on that output, using =INDIRECT(), "John" for example references table John (Manager) which contains the value "Mary" (Employee)
Basically, in my solution the key is using =INDIRECT() referencing multiple tables, VLOOKUP doesn't suit your needs in this specific case.
I have two SharePoint lists (only minimal columns described below for brevity).
The first has two columns, a text column called Name, and a person/group column called head of service.
The second has two columns, a lookup column called Service (which looks up from List1), and a text column called Value.
I would like to be able to create a view for the second list so it shows only the rows created by the current user AND any rows that the current user is Head of Service for - i.e. by looking at the relationship between the two tables and comparing the current user to the HeadOfService column in the first table.
I'm running in the Office365 SharePoint 2013 environment.
Since there's no way for SharePoint to read who is viewing a list and show different views based on that alone, the best you're going to get are pre-made views per user based on Created By and Head of Service.
I would like to create a database based on the following reasoning:
I want to assign to each contact I have some tags for his abilities, for example, so there will be a column called "abilities". So I was thinking about creating a list of possible abilities (probably on a second sheet), lets say "play football", "cook", "ride a bike" and define that "Mike" can "play football.
For this to be useful I would also like to know how it is possible to be able to filter my contacts by ticking on the list of abilities I am looking for.
There are a couple of ways to tackle this.
1) Make a table that has contacts and abilities all together. This means that you will repeat the contact info if a person has multiple abilities. Each row will be the unique combination of contact + ability. If you want to limit the options for ability to specific choices, create your list of abilities and use data validation to create a drop-down list of these values in your abilities column.
2) Make 3 tables: 1-Contact, 2-Abilities, 3-Map of Contacts to Abilities (each row contains the unique identifier for a contact and the unique identifier for an ability). I'm not sure if you really intend to make a database or just something in Excel that works. If you can use PowerPivot, that would be a good solution without needing another application to create your db. Bring your 3 tables into PowerPivot. Create a relationship between table 3 and table 1. Create a relationship between table 3 and table 2.
Ok - so here's the preface. I realize that SharePoint isn't really the best solution for this, and if I have to use SharePoint, then coding this would be preferable. However, my wings are clipped due to IT policy, and they have no time to do this "for me".
I am developing a document control system for an Environmental Management System. The basic concept is that there is a list of 'General Responsibilities', which identifies a regulatory agency, some category info, links to laws, etc... There's a second list 'EMS Responsibilities', which basically just links (via a lookup) a particular site to a general responsibility, to identify which sites have which responsibilities. We have many sites, and most have most responsibilities so it doesn't make sense to combine the two lists and repeat all this stuff 10x. Finally, I have a document library (for simplicty sake I am ignoring the draft/published libraries aspect) which contains the actual documents. These documents should reference an EMS Responsibility, which in turn references a General Responsibility. The categorization from 'General Responsibilities' needs to propagate all the way to the document library.
Currently, I use workflow to automatically copy the secondary lookup columns referencing the 'General Responsibility' to a 'Single Line of Text' column in 'EMS Responsibilities' so that it is available to the lookup in 'EMS Documents'. However, despite the values being present in both responsibility lists, the values do not propagate to my final list.
This workflow-based approach is stupid. The lookup columns are stupid. There's no way to get this to work elegantly using out of the box components. I want to believe that the reason this isn't working is because I am missing something... but I have searched for hours and can't find any more effective relational capabilities.
First of all, any theories as to why the values do not end up in the final list despite referencing a single line of text column that is filled?
Second, is there a better overall approach that doesn't rely so much on workflows copying data back and forth, and these pathetic lookup columns?
Thanks in advance!
Given the requirements you gave above together with your answer to my question I believe you won't need a workflow to link all three items together. I have two options for you:
1st Option:
Create a General Responsibility list. This list should contain at least two columns. The ID and Title column.
Create an EMS Responsibilities list. This list should contain at least three columns. The ID, the Title column and a lookup column linked to the General Responsibility list.
Create a Document Library. Add a lookup column linked to EMS Responsibilities.
Since the lookup list you are using is already linked to General Responsibilities then there is no need to have another column solely dedicated to point to General Responsibilities. If however, you need to have specific columns in your document library so that it explicitly has columns for both General Responsibilities and EMS Responsibilities use option 2 below.
Option 2
Create a General Responsibility list. This list should at least contain the ID and Title column.
Create an EMS Responsibility list. This list should at least contain the ID, lookup column linked to General Responsibility and Title columns.
Create a document library. You should add two lookup columns. One pointing to General Responsibility the other to EMS Responsibility.
(now the fun part starts)
Follow the guide to edit both your NewForm and EditForm aspx in this link so that your lookup dropdowns will be a cascading dropdown. This will make sure that items from EMS dropdown will only be populated once you select a value from the General dropdown.
Let me know if you need any more clarifications.
Any one has any idea how to map an infopath field to a sharepoint column of type choice? The infopath field is a repeating field, so the user can select multiple options, I want to be able to map those to the choice field in sharepoint. Any ideas?
update:
What I'm trying to do is the following. I have a choice column in sharepoint which allows user entered values. In infopath, I have a repeating field. I'm binding the field to a dropdownlist. The dropdownlist gets filled by a webservice. This dropdownlist is in a repeating section, so the user can choose to select from multiple dropdownlists. So lets say the user adds 2 dropdownlists, and selects an option from each dropdownlist. I want to be able to add those selections as choices in the sharepoint choice column.
SharePoint list is a flat structure, and because of that Infopath does not allow you map repeating sections to list columns.
You might wanna consider the following workaround:
Store Infopath form to one library
(along with non-repeating fields)
Use one of these custom activities to extract data from
repeating table and copy it to
another list
Create a custom data view or a web part to display these items (if
necessary)
This approach can be useful if you need to do some additional tasks with the repeating data.
When you are promoting fields within a repeated section into SharePoint columns, the options available are to promote the column as:
first (i.e. only the first selection is promoted)
last
count
merge (I believe this merges all the selected values together into a single entry)
screenshot http://img4.imageshack.us/img4/5539/repeatinggrouptr3.png
Is it not similar to Create a Repeating Cascading List from:
a Flat Data Source or
a Hierarchical Data Source ?
If it is, may be those two articles may give you some pointers.
Depends on the type of choice field it is.
If it is a Multiple Select (checkboxes) Choice field, you can set the field through the object model (from the sharepoint site) or through the web service, by using ";#" for each item that you want to check mark, where is the value which is listed by the checkbox. I don't remember what the option is for single choice only, but it is something of the same nature. If you are talking about lookup fields, it has to do with the index number of the field from the list you are looking it up from. Also, there is additional steps if the choice field allows users to input or specify their own options.