Tag Info

Hot answers tagged

4

You would need to create your own subclass the DataFormWebPart. Once that is done, you can expose simple text properties by adding attributes like these to the WebPart property that you wish the user to be able to change. [WebBrowsable, WebDisplayName("User name"), WebDescription("The Full Username"), Category("SomeCategory"), ...


3

First of all, OOTB WebParts are not officially supported to work on Application Pages in SharePoint. As I was told, it could be learned from official MS course 10232. And despite of that webparts in Application Pages actually will work in some cases, there are many potential problems with them. For instance, if you provide XslLink to a OOTB XSLT-webpart, ...


3

Open the web part page that contains the web part in question. In the web part parameters in Sharepoint Designer, you create a new query string parameter. Then you filter the web part so that your desired column is filtered by that parameter. Then you pass in the desired value in the query string and you should get the desired results.


2

You can do this by adding a Data View Web Part (DVWP) to the page in SharePoint Designer. In your DVWP you'd use an AggregateDataSource containing both the parent and child lists. The DVWP can grab the item ID from the Query String and use it as a filter value. It sounds like what I'm proposing is what you're already doing, perhaps, but this should at least ...


2

Here is a much better example by Ton Stegeman: http://www.tonstegeman.com/Blog/Lists/Posts/Post.aspx?ID=85


2

I had the same issue with all the controls using the Asset.js like PublishingImage and PublishingHyperlink field. After a bit of head banging, I figured out that the issue has been caused by the Windows KB update KB2844287 which I think got updated last night. Uninstall it and restart the box and the fields should start working fine.


2

There isn't anything in the SPD GUI to accomplish this. You would need to do it like you are doing it in the XSLT. Other way would be to use a Visual Studio solution, but you would be doing even more code that way.


1

The user profile service returns the manager as a string in the domain\username format. You could use that to make another call and pull in the value via joined subview possibly. If the field were returned as a user field like a normal person/group field in a list you could use the person.title field. This is not the case however and we just get a ...


1

Microsoft released a hotfix, no need to uninstall KB2844286 http://support.microsoft.com/kb/2872441


1

If you could implement the drop-down boxes in client side code (which also might be a nicer user experience) you should have a look at cascaded drop-downs from SPServices on codeplex.


1

could be a couple of things! as your using xslt it could be somthing simple ;) Simply change the &nbsp to &#160 for the XSLT code will solve this problem. Unable to display this Web Part. To troubleshoot the problem, open this Web page ... & Error: Reference to undefined entity 'nbsp' It is indeed a little weird. ...


1

try replacing this: <input type="button" value="Save" name="btnSave0" onclick="javascript: {ddwrt:GenFireServerEvent('__commit;__refresh;__redirect={Page.aspx?SelectedID_x003D__x007B_@ID_x007D_}')}" /> with <input type="button" value="Save" name="btnSave0" onclick="javascript: ...


1

Well following spending lots of time witnessing the above. Turns out simply putting the 'AssignedTo' in the ViewFields part of the query fixed the issue! Even though I'm not using the field for display the issue was fixed by adding it. The underlying fields are still different but SharePoint DOES KNOW THIS after all and the huge query produced references ...


1

This is what you'll need using ID's: CopyUtil.aspx (what's in a name, right?) http://weblogs.asp.net/jan/archive/2008/02/26/copyutil-aspx-a-little-sharepoint-gem.aspx


1

You shouldn't need to use the /../../ method if you are directing to a _layouts page. You could simply do it as (not fully tested, going from memory): <a href="http://your.spdomain.com/{@FileDirRef.urlencodeasurl}/_layouts/listform.aspx?PageType=4&ListId={@ListId}&ID={@ID}">text</a>


1

I assume you have setup User Profile Syncronization. There is a Filter Web Part for that, which should be able to benefit you from the Connectable web parts framework. Have a look here to see how is being used http://www.bjw.co.nz/developer/sharepoint-2010/97-using-a-current-user-filter-on-a-list To filter out items based on assigned permissions you could ...


1

If I understand you correctly you're inheriting from a Web Part which has XSLLink in the Category Miscellanous and you want to move it to Visual Settings. You should be able to do that like this: [WebBrowsable(true), Personalizable(PersonalizationScope.Shared)] [WebDisplayName("XSL Link")] [WebDescription("Link to XSLT")] [Category("Visual Settings")] ...


1

This sounds like it may be the double hop issue. In this instance you're asking the web server to impersonate the user with a request to another web service (regardless of whether its on the same machine or not) Unless you're using Kerberos, then you won't be able to use windows authentication as NTLM won't delegate. The fact that when you set a Username ...


1

It's interesting question. If you examine the code of RaisePostBackEvent method of DataFormWebPart class you will see the processing of such actionas as _connect, _update, _insert, _commit, _cancel, _refresh, _delete, _redirect and some others. For example on __redirect command DataFormWebPart executes the following code: else if ...


1

Ah stupid. You need to include <webParts> </webParts> inside the CDATA bit, otherwise it doesn't work.


1

Assuming you're deploying the DataFormWebPart through Elements.xml and <AllUserWebParts> element, you can use ~sitecollection and ~site tokens in order to get current site collection and current site URLs respectively. You can find some details and example code on this here. Another approach could be to fix WebUrl parameter default value in ...


1

One potential way would be to rely on the SPDataSource being able to query across sites in the same Site Collection, however as pre-requisite you need to either create your own Content Type with the data structure so you could target your query easier (or using a certain Template of list - the bottom line is to be able to "identify data") - instead of using ...


1

I don't believe this can be achieved without custom coding your own web part, or purchasing a 3rd party web part. You can try any of the popular vendors such as Lightning Tools, Bamboo Solutions, KwizCom, etc. Alternatively, you might try achieving this with a client side solution using Javascript (like the Client Object Model, JQuery, SPServices, ...


1

I was exploring this last week and have not found any way to make the URL dynamic. I tried the same methods. The only viable solution I found was to create it with jQuery and SPServices, as SPServices uses the current site as the default when hitting the web services. This comes with the detriment that everything is done client side rather than server ...


1

It works fine in my case. I added two different list data views to a page from the SP2010 designer and the ribbon works as expected. May be you should use XsltListViewWebPart and not DataFormWebPart.


1

I finally found the solution (helped by Marc and this blog post). Steps to success : Open in SPD the OOB dispform.aspx of the parent list In the same page, add a standard XsltViewWebPart or a DataFormWebPart. Use WebPart connexions to filter the data (Consume a filter from the OOB listformwebpart) This may also work with filtering data from the url ...


1

Apply the hotfix 953749 of WSS3.0 on code of form change the tag xsl named dvt_1 for this <xsl:template name="dvt_1"> <xsl:variable name="dvt_StyleName">ListForm</xsl:variable> <xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row"/> <div> <span id="part1"> <table ...



Only top voted, non community-wiki answers of a minimum length are eligible