What do you think of using email-enabled document libraries in SP2007? Is it reliable? secure? or too complicated to get it to work correctly?
Also would it accept emails from "anyone" sending to that address? What about other fields the document library may have (like for example adding a single line of text field to hold a classification field for example).
It is great for storing emails, building automated knowledge bases or easing publishing of articles to your intranet.
I encountered problems when a large amount of emails are being sent at the same time (e.g. when error alerts are being emailed). We wanted to trigger approval workflow for each item but if more then 10 emails arrived workflow did not fire on each item.
As Laney pointed out it also missed some "intelligence" to route email or to join same conversations together. Microsoft CRM has much better engine for handling incoming emails.
Conclusion: It is a nice feature if you are aware of its limitations.
but I can't find anything ideal, or even just something I'm semi happy with. I'm hoping that people could answer with ways they can think of for using a workflow to drive further document creation... or automatic creation of an accident list item. Now the process will need to have a set of official forms filled in by various people. This is where I find SharePoint limiting me with it's document centric nature. Typical workflows are about the document, like getting it approved or reviewed or some such. In this case the workflow needs to create new documents, InfoPath forms perhaps. Using task forms
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... 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...); properties.Add("FilenameCode", code); // Create the set DocumentSet invoiceSet = DocumentSet.Create( list.RootFolder, code, InvoiceSetContentTypeId, properties, true); What's not working: icon
column is used in document libraries in subsites as a required field. When we upload anything but an Office 2007 document, the user is presented with the document metadata fill-in screen (EditForm.aspx?Mode=Upload), the user fills in the appropriate data (including picking a value(s) for this lookup), and clicks "check in" - the document is checked in as expected, with the lookup field's value filled in. With an Office 2007 document, this fails. The user selected values for the lookup field do not ever make it to the server - no errors are thrown, but the field is not saved with the document
Is it possible from the MOSS 2007 OOTB web parts with no custom code of any sort to create a view of all document libraries on a given site expanded to show all folders and documents within it? Table of Contents will give you the libraries and CQWP will give you the documents but I'm looking for a combination of these I guess. I pretty sure it's not possible OOTB but thought I would ask this here just in case. Considering a DVWP to deliver the functionality but could save time if we can do this OOTB. NOTE TO SELF - Stop end users from using document libraries as folders!
On MOSS 2007 SP2, I have an announcement list that had audience targetting enabled. Users have email alerts set on that list for when new items change. The email displays the tartget audience as a guid - is that normal? I tried to google for the information, but the closest I could find talks about the problem showing up in the version history.
approval for the request. So far, my workflow uses the "Collect Data From User" action and the "Send and email" action. I configured data collection option so that there are two inputs: two radio buttons for approve/reject and a comment field. I built the email body and subject using dynamic strings and variables from the form data. I would like this approval process to be simple for the person.... I haven't found an easy solution like that, so I went with sending an email and creating a task. There are a few problems with this method: The email that is sent when the task is assigned
I am facing problem with document check out in a SharePoint document library. This is the message I am getting: alt text http://img11.imageshack.us/img11/1575/libraryerror.jpg I'm using the out of the box document library. I have logged on as Admin Document is not already checked out I have tried creating a new document library I have tried creating a new site collection UPDATE 1: Check out works with Firefox but not IE. UPDATE 2: No 2003 products are installed. This happens with all users. When I check out a document in-place (locally), check out works fine... This might be an IE
I have a couple of libraries that share a term store field for Clients. I put two list views on a page and planned on using the term store navigator to filter the lists, but couldn't find it in the filter section or any of the other available web part categories. Is it not available? Seems strange to not have access to it outside of a regular library.
I was asked a question today that I didn't have an answer to. There's a requirement to tag all documents uploaded to any document library within the web application with a selection from a choice field. IE: user uploads document, selects one of the choices as part of the check-in. My question is weather I can use a feature to add that column to every document library within the web application. The issue of adding it to new document libraries isn't a huge deal, but retrofitting all of the existing libraries would be a bit of a chore. I built a site column so that the choices would be managed