InfoPath Dev

A user is going to click on button and get a "Sum" of points earned from a DB table. SQL Server, i.e.

select sum(pointEarned) as TotalPoints from <table x> where username = user name stored on the form.

I created a "view" that stores the sum's for every username in the db.

I added the view as a secondary datasource. all the fields show up in Infopath.

I created a stored procedure that queries the "View" passing in username as a parameter.

I have added the fields of the "View" to the form with a "Run Query" button. Behiind the button I wrote Java script code to call the stored procedure passing the username paremeter.

I expected the results to populate the datafields for the "View" on the form.

Nothing happened.

Is this approach even possible? Using a SP, to query a "View" that is linked in as a "Secondary" Datasource?



Nothing happens when I run it.

Why do you need to use a stored procedure at all? If you just add the DB view that you talked about that has the sums already computed as a secondary data source then you should be able to filter this list on a name value. Are you receiving the list of username/sum pairs into InfoPath? If so, then there is no need for a stored procedure.

If you need to use a stored procedure for some reason that I do not know, there are several posts on this forum about this. Check out this thread for starters:

http://www.infopathdev.com/forums/topic.asp?TOPIC_ID=1863&SearchTerms=output,parameter

Matt, Thanks for replying. I hope you are right that I don't need the SP. I did read several threads on this site as well as others and couldn't find an answer.

Anyway, with your suggestion. Yes, the view coming in already has the data I need. How do you filter on a secondary datasource?

There is a username on the form when it opens. Let's say it is JaneDoe. I want to put a button on the form that filters the secondary datasource (which is a view) by username JaneDoe thus returning the "Sum" total of all her points.

Matt,

Thanks for the direction. I did more digging and found other threads that discuss filtering the secondary datasource and we got it to work.

I'll probably come back to the Stored Procedure at some point, but right now, we are going to just use the Filters.

Thanks!