Sorry to be so lax in my postings. I was really busy getting ready for PDC and now Beta1 for Office looms somewhere on the horizon. Please check out Rob Mauceri's blog on our plans moving forward.

Additionally, check out this article on MSDN which documents the DDWRT (data driven web runtime) functions available in the DataViewWebPart. This was done with a lot of work from Serge Van Den Oever as well as our dev team.

Thanks!
-John

If you ever see this error, and you are positive the item does exist, the most likely cause for error is that the URL does not contain the RootFolder attribute. As an additional side note, for some reason the DataView converts the EDIT link into the DISPLAY link, so there are two issues here that I will show you how to fix.

First, for the repro: Browse to the Shared Documents document library in the browser. Create a new document called docOne.doc. Create a new folder called FolderOne and browse to this folder. Create a new doc in this folder called docTwo.doc.

Next you want to open the site in FrontPage and create a new WebPart page. Then click Data..Insert WebPart. Choose the Shared Documents web part and insert it.

After it is inserted, right click it and choose List View Properties. Click Fields and add the Edit field. Then right click the List View and choose "Convert to XSLT Data View".

Save the page and preview in browser.

You should notice that if you click to edit docOne.doc, you see the Display form (which is wrong)

If you click to edit docTwo.doc, you will see an item doesn't exist error (which is also wrong)

So, back to FrontPage to fix this:

In code view for the page where the DataView lives, find:

<a href="{$URL_DISP}?ID={@ID}" onclick="GoToPage('{$URL_DISP}?ID={@ID}');return false;" target="_self">

And replace it with this:

<a href="{$URL_EDIT}?ID={@ID}&amp;RootFolder={@FileDirRef}" onclick="GoToPage('{$URL_EDIT}?ID={@ID}&amp;RootFolder={@FileDirRef}');return false;" target="_self">

That should do it. Have you seen other problems with Document Libraries? Let me know (the fact that the folders don't show up in the above scenario is already known and is unfortunately by design...)

-John

Hi,

I was just asked a great question: "How do I create a hyperlink when using a Lookup field that points to the item for that lookup field..."

This is not completely straightforward, so bare with me. In this example, I am using the Announcements list and the Contacts list. In the Announcements list I created a lookup field the LastName value in the Contacts list and have created a few announcements with the LastName value in them.

1. I need to get the List Id of the Contacts list. You can use the web service for this, but I find it much easier to simply drag the Contacts list onto a new page in design view, switch to code view, and Find '@ID' and then grab the list ID (it is a GUID). Then I close that page without saving it.

2. Create a new page

3. insert a view of the Announcements list including the Lookup field 4. select the Lookup field data value 5. Insert > Hyperlink 6. type the following into the URL address field:

https://server/subsite/Lists/Contacts/dispform.aspx{ddwrt:URLLookup('{LIST-GUID-FOUND-IN-STEP-ONE}', 'lookup', string(@ID))}

(NOTE The nested {} around the GUID).

My URL looks like this:

{ddwrt:URLLookup('{BBD5C595-B540-4839-AAAF-7FB2555A0960}', 'lookup', string(@ID))}

7. Save the page

8. switch back to code view and find "mailto:"

9. Delete this. It is a bug that when your URL has an @ symbol in it, FrontPage adds the mailto: code...goofy, but should be fixed in the next release.

10. save the page again

11. Preview in the browser

12. click the Link

NOTICE: You should be directed to the dispform.aspx page and see the contact information.

We are chugging along with the next version of Office and are super busy around here trying to get the right features into the next version of the Data View and SharePoint customization story. That said, I was looking through some older posts and saw this one:

https://blogs.msdn.com/frontpoint/archive/2004/04/30/123982.aspx

from Rob. This is a really cool feature for showing the count of items in your view. However, this count is not accurate once you start using Ad Hoc filtering. This post is about extending the above example by making a minor edit to the XSLT in code view.

So....

• Create a Data View of some data source (I'll just assume you know how if you're still reading this post)
• Click on Data then Style
• Enable the default toolbar and the Show View Footer checkboxes on the Options tab and click OK
• Drag some data value into the View Footer and use the OOUI to change this to a COUNT (this is how far the above article gets you, this next step is the Money step)
• Switch to code view (this next part is a little complicated - you are going to modify the View Footer XSLT and then move the code that says where to display the View Footer*)
1. Click Edit and then Find
2. find the following: dvt_1.footer
• the code should look like this:
•                     <xsl:call-template name="dvt_1.footer">
                          <xsl:with-param name="Rows" select="$Rows"/>
                      </xsl:call-template>
3. select this code and CUT
4. Click Edit and then Find
5. find the following: groupend
• the code should look like this:
•                     <xsl:variable name="groupend"><xsl:value-of select="ddwrt:NameChanged('', -1)"/></xsl:variable>
                       </xsl:if>
                       </xsl:foreach>
                       </xsl:template>
6. paste in the code from step 2 immediately after the </xsl:foreach> so it looks like this:
•                     <xsl:variable name="groupend"><xsl:value-of select="ddwrt:NameChanged('', -1)"/></xsl:variable>
                  </xsl:if>
              </xsl:for-each>
                      <xsl:call-template name="dvt_1.footer">
                          <xsl:with-param name="Rows" select="$Rows"/>
                      </xsl:call-template>
          </xsl:template>
7. click Edit and then Find
8. Find the following (again): dvt_1.footer
• The code should look like this:
•         <xsl:template name="dvt_1.footer">
              <xsl:param name="Rows"/>
              <table cellSpacing="0" cellPadding="4" border="0" width="100%">
                  <tr>
                      <td class="ms-vb"><xsl:value-of select="count(/dataroot/Categories/CategoryID)"/></td>
                  </tr>
              </table>
          </xsl:template>
9. Remove the <table> code so it looks like this
•         <xsl:template name="dvt_1.footer">
              <xsl:param name="Rows"/>
                  <tr>
                      <td class="ms-vb"><xsl:value-of select="count(/dataroot/Categories/CategoryID)"/></td>
                  </tr>
          </xsl:template>
10. Change the Count code so it references a variable rather than a literal path
•         <xsl:template name="dvt_1.footer">
              <xsl:param name="Rows"/>
                  <tr>
                      <td class="ms-vb"><xsl:value-of select="count($Rows)"/></td>
                  </tr>
          </xsl:template>
• Save the page and preview in the browser
• Change the Filter and you should see the count change

I am hoping this will be much easier in the next release.

-John

*technical details: our design is to put the view footer outside the body template that displays your data. Because of this, the scope of the $Rows parameter is outside the current Repeating Data Region. What we have to do is move the scope inside the current RDR. In doing so, we need to delete the <table> code so it will be valid HTML.

https://weblogs.asp.net/soever/archive/2005/01/03/345535.aspx

I was hoping to get some feedback about whether this information is useful, high priority, necessary...any comments at all.

Thanks!

-John

If you use FrontPage Behaviors to do things like change the background color of a layer, or change the style of a font tag using onclick or onmouseover commands, and you also want to restore the style onmouseout or onblur, you may find that the style is not restored properly in certain cases.

These cases are when the style is set as part of the style attribute. For example, if you have:
<DIV style="background-color: red;">this is in the div</DIV>

And you use FrontPage's behaviors to change the color to black onmouseover, it will not turn back to red onmouseout even though you check the box for it to do so.

The workaround if pretty simple, but also very hard to figure out, so here it is:

In code view, use Edit > Find to find the following code in the restore javascript function:

eval("x."+x.n+"=x.v"); }

and change it to:

eval("x."+x.n+"=String(x.v)"); }

That should do it for you.

-John

My code sample assumes you are using the default Announcements list on SharePoint and that the Title field is what you want to display.

First, browse out to your Announcements list (which you get by default when you create a SharePoint site), and add a few Announcements all with the same title (just for demonstrations sake :-))

Then...

1. Insert a Data View Web Part based on the Announcements list
2. Click Data..Style and change to the drop-down view style..OK
2. Probably best to switch to code view at this point
3. Find the code that looks like this:
<xsl:template name="dvt_1.body" xmlns:ddwrt="https://schemas.microsoft.com/WebParts/v2/DataView/runtime" xmlns:xsl="https://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt">
            <xsl:param name="Rows"/>
            <xsl:param name="FirstRow"/>
            <xsl:param name="LastRow"/>
            <xsl:for-each select="$Rows">
                <xsl:variable name="KeepItemsTogether" select="false()"/>
                <xsl:variable name="HideGroupDetail" select="false()"/>
                <xsl:variable name="GroupStyle" select="'auto'"/>
                <xsl:if test="(position() &gt;= $FirstRow and position() &lt;= $LastRow) or $KeepItemsTogether">
                    <xsl:if test="not($HideGroupDetail)" ddwrt:cf_ignore="1">
                        <option style="display:{$GroupStyle}">
                            <xsl:value-of select="@Title"/>
                        </option>
                    </xsl:if>
                </xsl:if>
            </xsl:for-each>
        </xsl:template>
4. Change that code to look like this:
<xsl:template name="dvt_1.body" xmlns:ddwrt="https://schemas.microsoft.com/WebParts/v2/DataView/runtime" xmlns:xsl="https://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt">
            <xsl:param name="Rows"/>
            <xsl:param name="FirstRow"/>
            <xsl:param name="LastRow"/>
            <xsl:for-each select="$Rows">
                <xsl:variable name="KeepItemsTogether" select="false()"/>
                <xsl:variable name="HideGroupDetail" select="false()"/>
                <xsl:variable name="GroupStyle" select="'auto'"/>

<!-- this next line is used to store the value we need to compare for uniqueness -->
                <xsl:variable name="uniqueTitle" select="@Title"/>
                <xsl:if test="(position() &gt;= $FirstRow and position() &lt;= $LastRow) or $KeepItemsTogether">
                    <xsl:if test="not($HideGroupDetail)" ddwrt:cf_ignore="1">
<!-- this next part is where we compare the variable created above to the current selection and if they are different, we write the value -->
        <xsl:if test="@ID=//Rows/Row[@Title=$uniqueTitle][1]/@ID">
                        <option style="display:{$GroupStyle}" value="{@Title}">
                            <xsl:value-of select="@Title"/>
                        </option></xsl:if>
                    </xsl:if>
                </xsl:if>
            </xsl:for-each>
        </xsl:template>
5. Save the page.  Notice that only the unique values are displayed.  You can use this code in any number of places in the XSLT (for example, inside a drop-down menu).

The goal of this article is to use an XML data source to populate a drop-down control that will take you to some other URL when you change the drop-down controls value. Now, if you are using List Data, you may want to check out my article for breaking up a URL field type. And I am going to post in just a minute or two with instructions for selecting unique values in the drop-down.

1. Open your page in FrontPage 2003
2. Data..Insert Data View
3. Choose your data source, right click > Show Data
4. Select the fields you want to use in the drop-down
5. Insert Data View
6. Data..Style
7. Change to “Drop-down view style”..OK
8. Switch to code view
9. Just before the </head> tag, add this code:

<script language="JavaScript">
<!--
function FP_jumpMenu(el,frm,sel) {//v1.0
var href=el.options[el.selectedIndex].value; if(sel) el.selectedIndex=0;
if('_new'==frm) open(href); else eval(frm+".location='"+href+"'");
}
// -->
</script>

11. FIND: <select name="ID" size="1"
12. Change to: <select name="ID" size="1" onchange="FP_jumpMenu(this,'window',false)">
13.  FIND: <option style="display:{$GroupStyle}"
14. Change to: <option style="display:{$GroupStyle}" value=”{@FieldWithURL}”> <!--where FieldWIthURL is your field with the URL J -->
15. Save the page and preview in the browser.

For each of these three statuses, I have a little gif image of a green arrow, red arrow and yellow circle respectively.  What I want to do is create a data view that has the name of the server and displays the arrow based on the what the status is. 

Here's how to do that.

1. Open the wss site in FrontPage 2003
2. Click Data..Insert Data View
3. Right click the SharePoint list that contains my data
4. Click "Show Data"
5. Select the Title field
6. Click "Insert Data View"
7. Since I only selected one field, I get a bulleted list. So I change this: by clicking on Data..Style > General tab and changing to Tabular view..OK
8. Place the Cursor next to one of the server names and add a new column to my view: Table > Insert > Rows and Columns
9. Place the Cursor inside a cell in this new column and insert my image
10. Insert > Picture from file
11. I type in the URL to the green.gif
12. Next to this image, I insert the red.gif and yellow.gif as well so each row of data now shows all three images
13. Select the green.gif image
14. Click on Data..Conditional Formatting
15. Click Create
16. Click Show Content...
17. I create a filter that says "Status == UP"..OK (now the green arrow only shows in rows where status is UP)
18. Repeat steps 13 through 17 for the other two gifs, setting the filter appropriately
19. Save the page

Using Conditional Formatting opens up a huge world of possibilities.  You can modify views by passing parameters via web part connections, you can format items conditionally, you can show data or hide data based on complex XPATH by clicking on the Advanced button in the filter dialog, and on and on.

For each of these three statuses, I have a little gif image of a green arrow, red arrow and yellow circle respectively.  What I want to do is create a data view that has the name of the server and displays the arrow based on the what the status is. 

Here's how to do that.

1. Open the wss site in FrontPage 2003
2. Click Data..Insert Data View
3. Right click the SharePoint list that contains my data
4. Click "Show Data"
5. Select the Title field
6. Click "Insert Data View"
7. Since I only selected one field, I get a bulleted list. So I change this: by clicking on Data..Style > General tab and changing to Tabular view..OK
8. Place the Cursor next to one of the server names and add a new column to my view: Table > Insert > Rows and Columns
9. Place the Cursor inside a cell in this new column and insert my image
10. Insert > Picture from file
11. I type in the URL to the green.gif
12. Next to this image, I insert the red.gif and yellow.gif as well so each row of data now shows all three images
13. Select the green.gif image
14. Click on Data..Conditional Formatting
15. Click Create
16. Click Show Content...
17. I create a filter that says "Status == UP"..OK (now the green arrow only shows in rows where status is UP)
18. Repeat steps 13 through 17 for the other two gifs, setting the filter appropriately
19. Save the page