I need to add a column to a SF listview that contains a link/button (like the .NET gridview) for the purpose of selecting an order from the list and clicking the link/button to navigate to another page to view/modify that order.



Also, since BO's are 'global' (for lack of a better term") in websites, does that mean if my record pointer is set on a specific record on page 1 it will still be on that record on page 2? or will I have to store the primekey as a session variable and pass it, then call an appropriate fill() ?



Thanks.




Keith Chisarik

For a link in the list view, you can use either the FormattedString and put something like <a href="mylink{0}.aspx">{1}</a> or you can use the PopulatedThroughEvent and just do it there. 

As for the record persisting between pages, yes, the entire business object is persisted between pages, so it will stay on the same record.

nice.........

Keith Chisarik

I am unable to reference the BO being used. I copied the code from the help files (winforms exampleas no webforms example exists) and this is what I get......



Intellisense properly fills in the BO types, p[roperties, and fields and the form will display BO data just fine so I am 99.99% sure I have things right.












Keith Chisarik

also, your link above would work if my pages were named individually, but of course I have one page to handle that, how do I access a value from the selected listview row to store it to a session variable for another page to load. I guess I just dont know what event to capture, I know how to read column/row values.

Keith Chisarik

also if you have any documentation in the works for webforms can I get it?



You can tell Steve I'll sign the waiver not to jump up and down if it isn't 100% since I assume it hasn't been through QC or we would all have it.

Keith Chisarik

I don't know that I have ever seen that error.  The only thing I can think that might be causing that casting exception is a version mismatch on your DLLs.  By default, .NET puts a * in the revision field for the DLL version number, which gets incremented each time you build.  So, if the version being debugged is different than the version in the AppDomain within VS, then the types will not match up.  That is really strange, though, since it seems that the types are exactly the same.

I have tried everything I know..... Please help.



I have rebuilt, cleaned, rebooted, re everything........

Keith Chisarik

I went old school and just pass a parameter in the URL to the review page..... so this is less pressing but if you figure out what went wrong with using the PopulatedThroughEvent population type with a BO, I would appreciate it.

Keith Chisarik

I've been looking at everything I can think of, and I have no idea where this might be coming from.  However, I will keep my eyes peeled and see if I can't figure out what was happening.