Databases
StackOverflow2013
Postsdbo
POCreating an XSLT Data View Form web part without Sharepoint Designer
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCreating an XSLT Data View Form web part without Sharepoint Designer
    primarykey
    data
    text
    <p>With Sharepoint Designer there is a feature that allows you to convert a web part list to an XSLT Data View (right click on the web part in SPD and click 'Convert to XSLT Data View'). I need to be able to mimic the control that is being created with this process (from what I can tell it should be Microsoft.Sharepoint.WebPartPages.DataFormWebPart). My host does not allow the use of SPD, so this webpart must either be out-of-the-box or bundled into a WSP. Unfortunately I am not finding a way to do this.</p> <p>Things I have tried:</p> <ul> <li><p>Saving the web part as a .webpart in SPD then deploying it as a custom web part. I get an error when attempting to add the web part to my site 'Type not found or is not safe' (something like that). The Microsoft.Sharepoint.WebPartPages.DataFormWebPart is not safe?</p></li> <li><p>Creating a DataViewForm web part through the browser and adding the same XSLT/Parameter code that is stored with the web part converted using SPD. Adding the code does not appear to have an effect (nothing happens).</p></li> <li><p>For testing purposes I converted a list web part to an XSLT Data View using SPD, then modified the XSLT/Parameter code through the browser just to see what would happen, and it worked fine. I think that at least gives a clue that the pasting in the code like this should work..</p></li> </ul> <p>My goal is to be able to create a menu system similar to this (which uses spd to create it): <a href="http://blog.pathtosharepoint.com/2009/01/15/a-drop-down-menu-the-sharepoint-way/" rel="nofollow">http://blog.pathtosharepoint.com/2009/01/15/a-drop-down-menu-the-sharepoint-way/</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USferr
    1. USferr
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCreating an XSLT Data View Form web part without Sharepoint Designer
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCreating an XSLT Data View Form web part without Sharepoint Designer
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMade some progress. Removing the ViewFlags value in the .webpart, then adding the .webpart through the browser works (otherwise I get a view is invalid error). I still get the type not found error with a wsp deployment of the same .webpart
      singulars
      1. POCreating an XSLT Data View Form web part without Sharepoint Designer
      1. USferr
    2. COAplying the viewflags fix to the .webpart and deploying it through a wsp gives me a new error "Unable to display Webpart ... The server returned a non-specific error when trying to get data from the data source"
      singulars
      1. POCreating an XSLT Data View Form web part without Sharepoint Designer
      1. USferr
    3. COAre you using SharePoint 2007 or 2010? If it's 2007, I'm surprised a host would allow .wsp deployment but not SharePoint Designer access. Have you looked at fpweb.com
      singulars
      1. POCreating an XSLT Data View Form web part without Sharepoint Designer
      1. USTom Resing
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload