I'm trying to create a link from a work item to the current server version of a file in TFS via the API. I can do it within Visual Studio (2012) so I know it's possible.
However when I try and do it via code it fails with TF201038: Linked item does not exist or access is denied. See Work Item Permissions for Links (http://go.microsoft.com/fwlink/?LinkId=75624) for more details.
The link doesn't really give me any helpful suggestions.
The workitem and the object are both objects that I've created and just gone and got out of the VCS. The link type I'm trying to create exists because I've checked against the WorkItemLinkTypes.
I've created the correct ends for the link types and added a new related link to the workitem.
It's only when I do a WorkItem.Save that it gives me the error.
The workitem isn't access denied, isn't read only or anything odd like that.
Have I missed something ?
I guess you are using the wrong link type.
You should not use the WorkItemLinks property nor the WorkItemLink class. Instantiate an ExternalLink object and add it to the WorkItem.Links collection instead.
You can find sample code at TFS2010: How to link a WorkItem to a ChangeSet.
Related
I randomly receive the error below on Office 365 SharePoint online when I go to a document library or custom list or trying to add a new item.
Something went wrong.
Unable to get property 'onDismiss' of undefined or null reference.
When I look at developer tools, I see this .js file being referenced splistitemsscope-is-mini-<>.js
Not sure where to begin to troubleshoot. Is anyone else getting this odd message?
I have this problem as well after migrate a list from SharePoint online to another SharePoint online teamsroom.
Cannot add a new element and also not edit an element.
I see there's been quite a few topics covering this error on Sharepoint, but not quite one where it happened to someone who's been using SSRS.
So I have this report which users need to access, with most of them it opens fine and they can use it.
But recently, two new users can't open the report.
They get the following error:
I tried to google and see whats wrong, but I cant find anything.
I'm having an issue, I created a custom table, added it to my customization project as a new DAC. The code is there, but how do i call this in a graph? I tried instantiating it as its own object, tried performing a pxselect, creating it as a viewname. None have worked for me, I looked through the documentation for "Generating a Data Access Class" And that doesn't apply to the ERP framework i get errors trying to generate class via that process.
Any ideas on how i should implement the new DAC to be accessible in my graph?
Thanks!
Found the solution, I incorrectly called my PXselect initially.
public PXSelect<UsrKSPOReceiptWeightSplit> WeightSplits;
Take your extension class from the AppRuntimeCode folder and cut/paste to your VS project folder. From there you can access your custom fields etc. Today in the Acumatica framework this is the procedure until this is fixed in the future. In the T300 manual this is covered in detail.
Here's a summary:
1. In Customization Mgr - create your data extensions
2. In VS copy the files that CM creted to your project to get a reference
3. Compile your extension library
4. When publishing your project you will have to delete your Customization extensions because there will be duplicates when you created your extension lib in VS.
This has been asked before but I'm struggling to find a way to delete a work item in Team Foundation Server. This looks promising:
http://devmatter.blogspot.co.uk/2009/04/deleting-work-items-in-tfs-ui.html. But no luck with it so far.
First tried the following command:
witadmin destroywi /collection:"https://<<my TFS collection>>" /id:1223
It returned Unable to destroy work item(s) 1223. TF237090: Does not exist or access is denied.
Unfortunately I can't download the "Delete Work Item" utility mentioned in the article due to work's internet restrictions as it's on Skydrive. Also tried the "TEK workitem" extension (mentioned in a comment at the bottom) but this won't let me either as I'm not a Project Collection Administrator.
Am I doomed to be stuck with this work item forever or is there any other way?
Yes it's a little annoying. Setting the item state to "Removed" will at least hide it from view.
Having a problem deploying a list instance via a feature, which should really be a noddy task, I know. I have come across many a post with the same issue, but there is no resolution.
I created the list in the UI with content and views.
Exported the site template as WSP.
Imported into Visual Studio the list instance, pages module and property bags.
Copied into my new solution.
Deploy list instance as a site-scoped feature.
List deploys fine with content and views. However, I receive the following error when trying to add a new item: “Unable to find the default new form for list”. The same applies for editing items.
Strangely, deploying via a web scoped feature works just fine.
I am thinking that this is probably something quite simple but cannot see it nor find a satisfactory resolution.
Many thanks in advance.
I discovered almost the same thing this afternoon, and solved it. For some reason the schema.xml has an empty Forms tag. You need to replace it with the stock forms tag as described by Microsoft - I wrote it up here;
http://notes.jonbeckett.com/2012/04/20/missing-forms-schema-with-sharepoint-2010-visual-studio/
The Microsoft page I discovered it on is here;
http://msdn.microsoft.com/en-us/library/ms459356.aspx