So I recently had a nice hitch in the SharePoint app I made for my client. We have a Document Library which is supposed to contain PDFs, converted from drawing files made in other programs. The test system has been deployed for public testing for his clients. This is real site usage, by the way, so real corporate data is being transfered. The site had been tested to be stable on the code side of things, but naturally I failed to take into account user-based errors. The testers uploaded a file in its normal file format instead of converting it to PDF first. And it's already passed through the entire first leg of the approval process before anyone caught this. I plan to implement this question's answer in the future to prevent this from happening again, but now I need to fix this current situation.
Because this is a real field test, I cannot simply upload the new PDF file and run it through the process, I need to maintain the field data from the original file, in all of its versions as well. Is there a way I can somehow upload the PDF as a new version of the original file?
Open your site/document library with SharePoint Designer and rename the file from the Designer UI. In my test case versions were preserved.
I initially thought you could do it from Windows Explorer view but it does not allow you to change the extension (on Windows 7).
One of the functionalities advertised for Office 2010 was that "People can access document templates stored in SharePoint 2010 via the New Document Wizard in Microsoft Office applications" (see page 26 in the PDF "Business Productivity at Its Best: Office 2010 and SharePoint 2010). However, I can't find a way to set this in Office 2010 applications. I've looked at Workgroup Templates (Word 2010 -> Backstory -> Options -> Advanced -> File Locations...) - I can't store URL or UNC paths - or even a mapped network drive to the SharePoint document library. Trusted Locations (Word 2010
I have a document library using a document set content type. I can create a new document set through the UI and it works perfectly. I'm now trying to create a document set in this library... for the set looks like a folder instead of the document set icon clicking on the document set doesn't show the document set home page, it just behaves like a normal document library running CAML queries shows that both internal fields HTML File Type and ProgId should be SharePoint.DocumentSet but instead they are blank changing a field value on the document set folder doesn't propogate to its contents
these documents should replace 2 of the existing documents from the original 5 - so that only 5 documents are ever displayed to Martin or John. John must not be able to see the original 2 documents that have been replaced. A small amount of luck is that an administrator will specify which new document should ‘replace’ an existing document from the originals. Over time I would be required to add more... on each individual document; I could add and remove these roles depending on whether Martin or John should be able to see that document. I think this would get really, really complicated. What other
have 11 pages of document links, each with its own subheadings. So far I have it set where each document has a custom field called "Page" with a check box list of all the document pages on the intranet site. On each individual page, I have setup a Content Query Web Part that displays the documents that have the corresponding Page value set (i.e. if a document Page value has been checked for "HR..., but these are the requirements I have been given for the project. NOTE2: It's also entirely possible that I am going about this the entirely wrong way (I'm new to SharePoint). If anyone could point me in the right
A common issue with my customers is that they define a number of content types that should be available on a document library. That library is part of a custom site template and pretty soon we'll have 200 sites using that template. Now the customer realize that they need two new content types on that library. Oh, and they will need those content types on the existing sites as well. I might have misunderstod something about content types or just misconfigured the library, but so far the only way I have been able to add those new content types on existing sites have been through a powershell
is causing this behavior? I can change the code to avoid it if I can figure out why it is happening. Is there any way through the SharePoint UI or APIs to "release" the document so that the original user can open it for editing? Is there any way through the SharePoint UI or APIs to tell who SharePoint thinks has the document open for editing (although in some cases that seems like it is going... if they just created the document (i.e., they clicked the button, the folder didn't exist, and so it creates the folder and copies the new Excel file into it). Sometimes they were working on it earlier
I have a doc lib that has several meta fields in it. I have a workflow that processes the doc based on these fields. Everything runs fine when the doc already exists in the library. If we add a new one by uploading (I havent tried New) the workflow doesn't fire properly. Looking at the debugger, when I click Upload, browse to select the file then click OK, the workflow fires. At this point, my meta data is empty as it's a new upload. Then SP sends me to the edit properties page for the doc (editform.aspx). I now fill out my meta data and click ok. The workflow doesn't fire again. If I go
is the customer specific file swap. My customer could create a new site for each of her customers, which would take care of almost everything, except that when she creates the new site, she'll need to download the masterpage from the root site and then upload it to the daughter site for the theme to apply across the board. That might be too much administration for her. If we didn't make a subsite... be overridden automatically (unless I can do it through SPD?). And my final option is to create a doc library for each customer. The issue here is when a customer logs in, how can I display a web part
I recently authored a C# based script for a blog posting, which copies column data from one file to another. While testing this solution I noticed that copying this data works differently depending on the file format, which is painful to say the least. For 'non Office 2007' files I can just assign the source file's Properties variable to the destination file. For Office 2007 files I need to write the destination file, iterate through all fields of the source file and then update the destination file again. If I treat all documents the same then either meta data is not copied over