Thanks Ryan,

I did actually figure that out late last night.

What threw me is that nowhere in the Dynamic View module documentation (that I could find), does it tell you how to reference tokens in querystrings for a url. And if you have never used DV before, but have used DF and DR, you would assume (as I did) that you would reference tokens the same way.

The only thing in the documentation that comes close to referencing tokens out of the templates section is on page 25 where it demonstrates using $(PrimaryKey) as the token to use in a SQL query as an example to delete a record from a table.

This was further compounded by one of only a few threads on this subject http://www.datasprings.com/dnn-modu...ews/#22013 which states:


"First Dynamic View:
Embedded in the link you can pass the $(PrimaryKey) value via querystring like this:

www.yoursite.com/yourView.ascx?DSParam1=$(PrimaryKey)"


It was only when I was staring at the template page trying to figure out what to try next, that i realized that the tokens were structured differently here, so why not try this structure in the querystring, and it worked.

I have to say, that I have a Love-Hate relationship with DataSprings' modules. I think that DF, DR, and DV combined make up a set of modules that no DNN site developer should be without.  With these modules I am now able to do things in DNN that I have always wanted to do. What I dislike, is the fact that it can take me hours to get something that should be very simple to work, such as this.

Maybe I am rare, but I actually read module documentation prior to using it. If this had been clear, and or demonstrated in the documentation, it would have saved me hours of time.

Don't get me wrong as I am not complaining, and I know that there is always a learning curve with new modules, I just wish that trying to get something as simple as this to work, did not take so long.

Steve

Patric,

Sorry for the late reply. I am sure that Chad's response was helpful, but to further illustrate and answer your question in regards to my initial post, this is what I did.

In my Dynamic View, I was viewing Users, and for the detail page, I was viewing the Events they signed up for. I wanted to be able to update those events in a Dynamic Form, so in the detail view template, I created a edit button with the following URL: MySiteName/MyDynamciFormName.aspx?DSParam1=[UserID]&DSParam2=[EventID]

Of course your Dynamic Form has to be confirgured to accept these DSParams via hidden fields on the form. I also passed these paramaters to the form's initial sql databind using the following sql statement:

SELECT FirstName, LastName, Email, OrgID, ProfID, SpecID, EVentID, DateIDs
FROM EventUpdate_V
WHERE UserID = $(DSParm1) AND EventID = $(DSParam2)

I Hope that helps.

Chad, as far as headaches go, this is not too bad if you know what you are doing, so I am not sure which would be better. Making the change as you suggested, or clarifying the procedure in the user manual. I will leave that one up to you.

Steve