![]() Again no parameters used in the stored procedure. Create another stored procedure to gather your parameter list values.It must generate all your report data upon execution This stored procedure CAN NOT have parameters. Using SQL create the stored procedure that gathers your report data.Hopefully that helps, even if it is 7 months late. even if you won't use that table again in the report. The main takeaway here is that the table, not a command, needs to be in the report in order to be a candidate to populate dynamic parameters. In both cases, CR will query the database twice the first time to simply get the entire list of reps and the second time to run the SQL Command. Now you can pull the sales reps into the dynamic parameter and use it in either the SQL Command itself as a parameter, or you can just use it in the record selection formula to filter results from the SQL Command. ![]() You can pull the table in next to the SQL Command that you're creating, and just link them however you want with an outer join so as not to limit your records (You could even not link them at all, but Crystal will complain about having "Multiple starting points" or whatever. ![]() ![]() To get the dynamic parameter to work, you'll have to add whatever table to the report that contains the 'sales rep' field. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |