I added a link-type with Forward=Task and Reverse=User Story using a Dependency. I uploaded this to my collection successfully.
Now I delete the link type and upload the template successfully again.
When I now want to create a new link type containing "Task" as Forward I get the error:
TF201006: The link type NEWNAME conflicts with link type OLDNAME. The name Task is already being used. (type ProvisionValidationException)
I don't see how to remove the OLDNAME.xml on my TFS because I don't know, where those uploaded templates are stored. Obviously the ProcessEditor will leave those files even if you remove a link type.
I got it. The LinkTypes are uploaded as entries in the LinkTypes-table on the SQL-Server-Database responsible for the team collection you upload the template to. So if you experience the same problems go ahead and delete all items from this table which are added by yourself.
Related
I'm implementing a WebDAV file server using the ITHit WebDave engine, i have the following problem
When i list the files and open one of them i get the ReadAsync method called, i provide the content and the file is opened correctly
However any changes i make to the file can't be saved, i get an error saying
A device attached to the system is not working
I looked at the file system samples and implemented support based on the FileSystemStorage.AspNetCore sample,
From what can understand the WriteAsync method is used when creating new files, should i expect for WriteAsync to also be called for file edits that need to be changed?
Am i wrong in the assumption that DavFile.WriteAsync will be called with a stream for the updated content?
If WriteAsync is not the right location to save updates to a file, could you provide some guidance on the process of saving changes to existing files?
Edited to add:
Now i can see that after i dismiss the first error about the device not working i get the standard save dialog box, if i click save it asks me if i want to overwrite the existing file, after accepting to overwrite then WriteAsync is called and i can update the file contents
I'm not quite sure why it would first tell me there's an error and then still allow me to write the file but only as replacement to the original file
Thanks for your help
Fixed, i found that there were issues with the ILockAsync implementation, reviewing the FileSystemStorage sample helped fix the issue with locking files before writing or updating properties
In my Umbraco cloud instance I can't see option to include contents within any child folder while using option "Queue for transfer". I can do this with home folder(top folder). See below screenshot.
Not sure if this is a temporary bug in cloud instance or there is any option I am missing. Can any one suggest if there is any option to transfer, content in chunk for child folders?
So, further chasing the issue with Umbraco cloud support, I found that it is a know issue with Umbraco cloud and for document type configured to show as list view. The work around for this issue is to disable the list view for document type.
I see a number of routes to upload various files into D2L, including News, Content modules and the like - http://docs.valence.desire2learn.com/basic/fileupload.html however, is there a route to update a file into the "Manage Files" area of an org? For example to programmatically create a CSV for the CCB tool and upload it to the proper location?
The org that I have is one for "Course Branding" and the content path is something like
go to the course->edit course-Manage files and the Url /content/enforced/7974-ACB/ and there are 4 subdirectories there. I'd like to create a file in one of the subdirectories but not sure what the route should be. Any ideas?
Chris
Currently, you can only add files to an org unit's Manage Files area if that org unit has course content, because you must use the course content APIs to add the file data. You must also create a course content topic of type file in order to upload file data to the course's Manage Files area.
The Url property for the ContentObjectData JSON you send up indicates where in the course's Manage Files area the uploaded file will get stored: it must therefore be a legal path within your course's existing content space, and a file name that's not yet been used. Note that you can't update the underlying file you've already uploaded, or delete it, through the API. However, you can delete the content topic used to insert the file in the first place: the content topic will go away, but the underlying file will remain behind in the Manage Files area.
This is not a pleasant workaround, but it does seem to be a workaround.
I am saving images on file and i am creating first folder which has Guid name for avoiding to duplicate file names. And entities hold reference src of image.
I feel that creating folder and giving guid name is wrong from point of performance. So how i have to avoid duplicate names ?
And second problem is the project seperated into 2 project. One is admin and other for user interface so i can not access my saved files from user interface. What is best practice about these problems ?
About the first problem, I think you could create a folder per user and replace the existing file, asking user confermation.
The second problem can be solved using a NFS or a shared directory where the admin and the user application can both read and write files (and you need to develope a component that retrieve the files and return them to your web apps).
I am using Web Part Connections to filter documents in a documents library in SharePoint. To do this, there's a column that is required, which I've named "related contact." Here's my problem: When I go add a New Folder (instead of just a document) SharePoint only asks me for a title for the Folder. The "related contact" column (which is required for the documents) doesn't even appear. Since the info on that column is empty, web part connections doesn't see the folder at all. Is there any way to make the Folder ask for another field at the time of creation?
Thanks
-V
Did you try creating a new folder content type with those required fields and trying to use that (and perhaps turn off the standard folders)?
Perhaps this page will help you: SharePoint folders and metadata.
Folders are one-dimensional. They are virtual containers for your documents, but aren't objects in your library that contain actual metadata.
Instead of using folders, I would recommend adding a column to your library that would mimic the names of the folders. From there, you can sort/filter/group/query the contents of that library. If users are sticklers for the folder structure, you could create a View that groups the documents by that new column, which would give you the appearance of folders.