[Forum FAQ] How to configure a Data Driven Subscription which get multi-value parameters from one column of a database table?

Question

Introduction
In SQL Server Reporting Services, we can define a mapping between the fields that are returned in the query to specific delivery options and to report parameters in a data-driven subscription.
For a report with a parameter (such as YEAR) that allow multiple values, when creating a data-driven subscription, how can we pass a record like below to show correct data (data for year 2012, 2013 and 2014).
EmailAddress                             Parameter                      
Comment
[email protected]              2012,2013,2014               NULL
In this article, I will demonstrate how to configure a Data Driven Subscription which get multi-value parameters from one column of a database table
Workaround
Generally, if we pass the “Parameter” column to report directly in the step 5 when creating data-driven subscription.
The value “2012,2013,2014” will be regarded as a single value, Reporting Services will use “2012,2013,2014” to filter data. However, there are no any records that YEAR filed equal to “2012,2013,2014”, and we will get an error when the subscription executed
on the log. (C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles)
Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportParameterException: Default value or value provided for the report parameter 'Name' is not a valid value.
This means that there is no such a value on parameter’s available value list, this is an invalid parameter value. If we change the parameter records like below.
EmailAddress                        Parameter             Comment
[email protected]         2012                     NULL
[email protected]         2013                     NULL
[email protected]         2014                     NULL
In this case, Reporting Services will generate 3 reports for one data-driven subscription. Each report for only one year which cannot fit the requirement obviously.
Currently, there is no a solution to solve this issue. The workaround for it is that create two report, one is used for view report for end users, another one is used for create data-driven subscription.
On the report that used create data-driven subscription, uncheck “Allow multiple values” option for the parameter, do not specify and available values and default values for this parameter. Then change the Filter
From
Expression:[ParameterName]
Operator   :In
Value         :[@ParameterName]
To
Expression:[ParameterName]
Operator   :In
Value         :Split(Parameters!ParameterName.Value,",")
In this case, we can specify a value like "2012,2013,2014" from database to the data-driven subscription.
Applies to
Microsoft SQL Server 2005
Microsoft SQL Server 2008
Microsoft SQL Server 2008 R2
Microsoft SQL Server 2012
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Answer 1

For every Auftrag, there are multiple Position entries.
Rest of the blocks don't seems to have any relation.
So you can check this code to see how internal table lt_str is built whose first 3 fields have data contained in Auftrag, and next 3 fields have Position data. The structure is flat, assuming that every Position record is related to preceding Auftrag.
Try out this snippet.
DATA lt_data TYPE TABLE OF string.
DATA lv_data TYPE string.
CALL METHOD cl_gui_frontend_services=>gui_upload
  EXPORTING
    filename = 'C:\temp\test.txt'
  CHANGING
    data_tab = lt_data
  EXCEPTIONS
    OTHERS   = 19.
CHECK sy-subrc EQ 0.
TYPES:
BEGIN OF ty_str,
  a1 TYPE string,
  a2 TYPE string,
  a3 TYPE string,
  p1 TYPE string,
  p2 TYPE string,
  p3 TYPE string,
END OF ty_str.
DATA: lt_str TYPE TABLE OF ty_str,
      ls_str TYPE ty_str,
      lv_block TYPE string,
      lv_flag TYPE boolean.
LOOP AT lt_data INTO lv_data.
  CASE lv_data.
    WHEN '[Version]' OR '[StdSatz]' OR '[Arbeitstag]' OR '[Pecunia]'
         OR '[Mita]' OR '[Kunde]' OR '[Auftrag]' OR '[Position]'.
      lv_block = lv_data.
      lv_flag = abap_false.
    WHEN OTHERS.
      lv_flag = abap_true.
  ENDCASE.
  CHECK lv_flag EQ abap_true.
  CASE lv_block.
    WHEN '[Auftrag]'.
      SPLIT lv_data AT ';' INTO ls_str-a1 ls_str-a2 ls_str-a3.
    WHEN '[Position]'.
      SPLIT lv_data AT ';' INTO ls_str-p1 ls_str-p2 ls_str-p3.
      APPEND ls_str TO lt_str.
  ENDCASE.
ENDLOOP.