New answers tagged

0

In your ItemStyle.xsl, create a new template and add this code. Make sure you publish it and select the template in the web part properties. <xsl:template name="Announcement" match="Row[@Style='Announcement']" mode="itemstyle"> <xsl:variable name="SafeLinkUrl"> <xsl:call-template name="OuterTemplate.GetSafeLink"> ...


0

The solution to have those appearing as they are is to query the exact list and not the whole site collection or site, which means it is not possible to content query multiple blogs (which will have to be mandatory as subsites). At that point the number of comments is 0 or whatever and the post category do show up. I had made the Author working because I ...


1

It is possible to query multiple subsite with a content query web part. You only need to find the correct match (display template) or be able to edit in XML the one that is closer.


0

There is another post regarding vanity URL's. This outlines ways to rewrite your URLs on the IIS. Link to post


0

Added modified SafelinkURL code in Itemstyle.xsl as 'code' 'code' reference the SAFeLinkURL in the appropriate site column as : 'code' 'code'


0

If you use search, like the Content Search web part, you can use a filter like {DepartmentMP={User.Department}} where DepartmentMP is the Managed Property mapped to the crawled property for the Department filed of the list or library and User.Department is the Department filed from the User Profile.


0

There is a solution I used few times but it's not the most elegant one. It is possible to create list views filtered on a Person field based on whether the current user is a member of a group or not. So this requires your budget customer list (for example) to have a Person field which allows Groups. Then you create a SharePoint group for each department and ...


3

You can turn audience targeting on the list. Go back to each of the files and target them to the appropriate audience and then just use one webpart that honors the audience targeting. You can better idea from steps mentioned in below MSDN article. Target list or library items to an audience Please check the content for Target list or library items to an ...


0

Check the Audience targeting for that web part. you sure you have not given any group name in the webpart. If it is a publishing site. have you published the page after adding the webpart? If it is in draft(or check out) state, it wont be visible to the users. Go to the library where page is residing and check all these properties. Ideally user should be ...


0

I do suggest to go with CSWP. The reason is it is very flexible and easy to use, but also very complex and can be customized to do amazing stuff. I know you mentioned that you dont want that much dev time, so I would say invest some time to understand the basics and it has a basic mode where you can just build the query based on drop downs and you don't need ...


1

I would like to add one line that this question seems to be Opinion based. So in my opinion if I have to work with the given requirement I will definitely go with CSWP. Because this covers all the above requirement specified. Because configuring search queries is quite easy job and take less efforts. For me this link had a great way to guide CSWP. Want to ...



Top 50 recent answers are included