I was asked to create a skills matrix for our company on SharePoint 2013 Online. Our company consists of about 400 employees.The skills matrix consists of 4 Categories with several fields under each category. Each field has three columns associated with it, Skill Level(1-5), When Last Used, Months Experience.
The goal:1. Fill out form on sharepoint.
2. Save to list- date created - created by
3. HR logs on and pull all skills for specific user into excel.
What I have tried:1. InfoPath form that saves to list. Problem : Unable to add four different repeating tables to add all related skills for that user under each category.
InfoPath form that saves to library. Problem : Unable to query data for HR
MS Access 2013 web app. Problem : Unable to add more skills under each category.Unable to associate one user to several skills.
I think the best solution is probably to go with Access. if anyone could please point me in the right direction to go about this?
or even if there is a better way of coding a custom app in visual studio?
Related
I am trying to learn SSIS to create SharePoint packages for our company site. Through trial and error, I have learned to create basic packages that will extract specific data from existing SP source lists and populate others.
I found basic information on the web that has helped me thus far. Unfortunately, I cannot find information on an order of procedure for effectively using some of the SSIS containers
As an example, I know that a SP List Source must be followed by a Sort before a Merge Join Transformation. However, I am uncertain if a Derived Column should precede a Conditional Split, or if it really matters. Additionally, there are 2 connection points on Derived Column and Conditional Split containers, one Red and the other Blue. I assume they are used to connect a Derived Column to multiple Conditional Split containers, or vice versa, but I really don’t know for certain.
Can anyone help by providing me with a web source that doesn’t just tell me what a container does, but how to use it effectively. I’m ready for the next steps, but I don’t have reliable connections to get the information I need. BTW... I am using Visual Studio 2012 and SP 2013.
Thanks in advance for any help that can be given.
I currently use TFS 2013 with custom work items for bugs, change request, requirements and features. I am wondering if I can migrate them to visual studio cloud 2015? is there a tool within VS or 3rd party that can do this?
If you are meaning the vsts. Possibly duplicate with this question: How to migrate work items from TFS to VS Team Services (VS Online) . There has been perfect answer from jessehouwing, suggest use one of below three ways as he suggested:
Use Excel for import/export - Will work for most work items, you loose attachments and work item links other than parent/child. The
trick is to extract from one Project Collection then copy all fields,
except the ID to an Excel sheet bound to the target project
collection. You will need to fix all Identity fields (works best when
users have the exact same display name on premise as in VSTS) and
you'll have to import once with state new and then past the current
state/reason over the just imported values and sync again. Test
Cases, Plans, Suites and Shared Steps will not be imported with their
relations in tact. The approach would be very similar to this
one.
Use the TFS Integration Tools - Will work for most work item types, though it will loose custom kanban states and tags. Test
cases, Shared steps and their relations will not be imported. This
option will allow you to import import work items and source code
with their relationships in tact.
Use a 3rd party solution - Out of the available options currently OpsHub offers the most complete solution. For test case and
source control link migration you're looking at the commercial
edition, which comes at a steep price. It still has a long list of
known issues and last time I tried it, I ran into numerous
issues which required their support to resolve them. PS: You can aslo try the tool as Dave suggested in the comment: VSTS Sync Migration Tools
My team currently works with an on-premises TFS 2012 server. I am migrating everything to Visual Studio Team Services, formerly Visual Studio Online. I am starting with a test project and was able to easily get all the code migrated, but can't figure out how to do the same for the work items.
Are there any good guides out there?
New options as of March 29th 2018:
TFS to VSTS migration - The official import option which will import 1 project collection into 1 VSTS account. It automatically imports everything stored in the backup. At the point of writing this, the TFS must be upgraded to TFS 2018 and some work item template customizations must be removed (there are a few well documented features unavailable on VSTS).
VSTS Sync Migrator - Marting Hinshelwood, the uncrowned king of TFS and VSTS migrations, has built his own little tool that can migrate work items from one server/account to another. It can even do migrations from one Team Project to another and while doing it switch between process templates.
VSTS Work Item Migrator - Microsoft has also open sourced a project that they used internally to migrate work items. It's less powerful, but it was made by Microsoft.
Previous answer:
At the moment there isn't a really good story. Your options are:
Start over - easiest :).
Start over and manually recreate items of value - It's a pain, but it's some teams have done these things in the past. keep the old TFS server available in read-only mode and each time you use a work item in the old system, you manually create it in the new one, set all the fields and upload the attachments. Depending on the number of items it'll take you a few sprints to migrate the most important stuff over.
Wait a while longer - Microsoft is currently working on a full fidelity import option which will allow you to upload a Project Collection and it will be exposed as a new VSTS Account (it's not going to be possible to import a project collection into an existing account).
Use Excel for import/export - Will work for most work items, you loose attachments and work item links other than parent/child. The trick is to extract from one Project Collection then copy all fields, except the ID to an Excel sheet bound to the target project collection. You will need to fix all Identity fields (works best when users have the exact same display name on premise as in VSTS) and you'll have to import once with state new and then past the current state/reason over the just imported values and sync again. Test Cases, Plans, Suites and Shared Steps will not be imported with their relations in tact. The approach would be very similar to this one.
Use the TFS Integration Tools - Will work for most work item types, though it will loose custom kanban states and tags. Test cases, Shared steps and their relations will not be imported. This option will allow you to import import work items and source code with their relationships in tact.
Use a 3rd party solution - Out of the available options currently OpsHub offers the most complete solution. For test case and source control link migration you're looking at the commercial edition, which comes at a steep price. It still has a long list of known issues and last time I tried it, I ran into numerous issues which required their support to resolve them.
There are specialized TFS consultants who live off these kinds of migrations if your current state of the work items is precious to you, then you could reach out to them.
See also:
https://www.visualstudio.com/en-us/articles/adopting-vsts
I want to express dependencies with links. A is dependent on B. I would like to be able to express that A needs B by some Date. Is there a way to annotate the link with a date?
Although it is valuable to understand your dependencies, especially if you have more than 2 teams working together on the same product you can't add dates to the link.
You can however add the rate to the feature or epic that are related. At this time there is no delivery date or required by date in VSO Associated with a PBI or a bug. Customisation of work items is due in the near future on VSO so that you can add that field.
Scenario : A web application with user login, roles and permissions.
Question :
Is it better to start with Visual Studio's / Visual Web developer Express edition's project wizard which contains the user management with it OR start an empty project?
If started with wizard, How can I move the membership and role Database tables to my own database?
Programatically working with Membership and roles. How?
If started with empty project, How can I manage membership and roles etc. ?
How to add new fields in user profile?
I am in student level in .NET. Above are some confusions I encountered while trying to start developing a project. It might be some silly question. Please do not ignore. Guide me with some helpful hints and good links if necessary.
EDIT:
I found a good tutorial here : http://www.codeproject.com/KB/aspnet/ASPDOTNETauthentication.aspx
It solved 50% of my problem.
It sounds like you need to start with some good tutorials on how to do authentication. Here are a couple that I think would be helpful:
http://www.csharpfriends.com/Articles/getArticle.aspx?articleID=70
http://www.youtube.com/watch?v=8t1MoIsMUKE
Because you have a student level understanding of .NET, I would recommend practicing a few times using these and other tutorials before trying to do everything you want to do.
As for wizard vs. empty project, I don't like wizards. There is too much I want to change and if I forget about something I end up with code bits hanging around and that is never good.
If you code the system by hand and store your authentication information in a database, you can manage the roles/permissions/etc. with simple SQL calls.