My organization is in the process of converting our intranet over to a SharePoint solution. Part of this intranet will be the movement and organization of all our internal documents. Currently, we 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" it will appear on the HR page). The goal of this setup is to allow the nontechnical personal who will be responsible for the maintenance of the documents to be able to upload new documents to the documents list and note on which pages they should appear on without having to manually update the pages themselves.
The problem that I am having is that I cannot seem to find a good way to sort the documents into their subheadings once they are on the appropriate page. I could create individual check boxes for each page/subheading combination, but this would create a list of approximately 50-75 items. Does anyone have any ideas as to how I could accomplish this, either via CQWP or by different means?
NOTE: I am aware that this is not the most efficient or elegant way to do things, 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 direction, I'd really appreciate it. I'll also provide any clarification that anyone needs.
Rather than indicating where the documents should be displayed, create columns for the document that indicate what the documents are (Content Types) or about (metadata). Then your pages can display things based on the characteristics of the document rather than where someone thought the document should go.
This is a better answer for many, many reasons, but the primary ones are scalability and advancement of enterprise taxonomy.
Further to Marc's answer about creating custom content types, you could also add the 'target audiences' site column to that content type. This would allow you to target specific documents at specific 'audiences' that you have created. You could have, say, a HR audience which is based off the Department user profile property, or just to get you started hardcode the value 'HR'. Then add the audience to the HR document site column (b/c this document is now based off your new content type you just created). Lastly add the audience to the CQWP.
that existed prior to the upgrade. This is also the case in a retract,delete,add,deploy scenario. Note: Our server topology has changed over time. Our Central Admin machine reached its End of Life, so we...We have a server farm that is having issues deploying WSPs. The odd thing is that the server goes through all the motions of deploying the WSPs with no errors. That is, the job is scheduled..., we were lucky enough to still have the soon to be decommisioned server that previously ran Central Admin (Server1). So, I added the server to the farm. Removed the Central Admin from the new Server
within the SharePoint front end. All of the web parts will need to automatically detect consumers and providers to create connections at runtime. What we are looking to do is have webparts discover and automatically connect to other compatible webparts. When a user adds the two compatible parts to a page, the parts should be able create the appropriate connections. We have a well defined interface for passing data between the parts, so the only issue is how to manage the connections. To be clear, we do not want user's to worry about having to create connections themselves. For our
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...SharePoint workflow by nature is document centric in that you have to have a 'thing'; A object for the workflow to run on. This object can be a document, form or simple list item but this thing has
I have 2 users, Martin and John I have 5 documents, all available to Martin and John. I also have 2 documents that are available to John only (Martin must not see them). To complicate matters... 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
though the new group is based on permissions that have been directly copied from a permission set that does allow page creation Does this make any sense? Can anyone help me to understand it? Update 1...Does anyone know what permission levels are required to allow a user to create content but not approve it? I’ve just spent the afternoon trying this and am more confused than when I started. For instance… If I add a user into the Designer site permission group I can create pages – excellent, just as I would expect. If I create a new site permissions level - let’s call it ‘customer-designer
(Windows6.1-KB974405-x64.msu) Enabled all roles indicated in the list (IIS and WCF) Installed Sharepoint Foundation 2010 didn't run the product configuration wizard (yet) created two additional domain user accounts without any particular rights: SPF_DATABASE for database credentials SPF_ADMIN for farm credentials Added domain administrator in SQL Server 2008 R2 with sysadmin rights started Sharepoint.../library/ee554869%28office.14%29.aspx and installed these: WCF Hotfix for Microsoft Windows (KB971831) ADO.NET Data Services Update for .NET Framework 3.5 SP1 Changed setup as explained on the web page Filter pack
(I have also asked this question on Stack Overflow) I have a SharePoint feature I'm using to add some custom aspx files to the Pages Library. When I activate the feature, I can visit the pages in-browser and they are visible in SPDesigner, but when I "View All Site Content" they are not there. Why is this the case? The Feature's Elements File: <?xml version="1.0" encoding="utf-8"?> <.../Pages/Example.aspx When I "View All Site Content" I am looking at the contents of the "Pages" list: http://myserver:PORT/subsite/Pages/Forms/AllItems.aspx
I have created a simple survey with SharePoint Server 2010 with the intent of allowing all our domain users to access and complete it. I added some basic branching logic to this survey as well... possible. Can anyone tell me what I may have misconfigured or need to change? Update I've worked with the problem a little more. If I just create a survey with one question using only a yes... they try to submit their answers they still received the Access Denied error. I have tried sending an access request from a test user (as prompted by the error page), but I still received the same error
only site collections/sites using non-publishing templates. All other content is availble e.g. documents, lists Has anyone else come across this? UPDATE 08/05/10: I have been doing some further... post Infrastructure Update - in my situation it was applying SP2 but it might have been one of the culmlative updates after IU A search pre-SP2 using contentclass:STS_Site as a filter will list all..." returns the webs or sites respectively. UPDATE 02/06/10: As I mentioned above an upgrade to SharePoint 2010 will fix the issue (at least make the STS_Site and STS_Web results appear again