Showing posts with label jump. Show all posts
Showing posts with label jump. Show all posts

Monday, March 12, 2012

Localization problem

Hi
I have a report with a "Jump to report" navigation field to a second report
, some of the parameters to the second report are DateTime values, when my
Local Settings are setted to English (United States) the link works fine,
but when I change my Local Settings to Spanish I get a Type Mismatch
message for this DateTime parameters. The "Language" property of both
reports are "Default", and when I execute by my self the second report
specifying each parameter with the correct locale datetime format it works
fine.
Any idea?
Thanksthis could happend because of session/caching of the subreport.
Click "Refresh" button on the toolbar when viewing the subreport.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> Hi
> I have a report with a "Jump to report" navigation field to a second
> report
> , some of the parameters to the second report are DateTime values, when my
> Local Settings are setted to English (United States) the link works fine,
> but when I change my Local Settings to Spanish I get a Type Mismatch
> message for this DateTime parameters. The "Language" property of both
> reports are "Default", and when I execute by my self the second report
> specifying each parameter with the correct locale datetime format it works
> fine.
> Any idea?
> Thanks
>|||Thanks for your answer, but I think that is not the problem.
Let me explain the problem again, I have a first report with two parameters,
"Start Date" and "End Date" that are used when the report is executed to get
some information from some DB for this time range, this information is
showed in a table where the first column values are links to other report
(not a subrerport), this second report also uses date range parameters and
its values should be the same of the first report parameters, this means
that also should be specified in the link.
So when I click the link to open the second report and I have Spanish or
other locale selected for my system regional options a type mismatch message
is showed instead of the second report:
"The value provided for the report parameter 'EndDate' is not valid for its
type. (rsReportParameterTypeMismatch)"
My intuition is that the problem is with the date format, the date format
for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy' I
think that the second report is trying to build its date time parameters
with the English locale and here is where the exception is raised. E.g. set
a value greater than 12 as month.
When I execute the second report specifying the parameters values manually
with the correct locale date format the report is showed without problems.
When I see the "Language" property of both reports in design mode is set to
default, I suppose that means that the report should works with the system
locale settings and use the correct date formats.
Thanks
Mauricio
"Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
> this could happend because of session/caching of the subreport.
> Click "Refresh" button on the toolbar when viewing the subreport.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> > Hi
> > I have a report with a "Jump to report" navigation field to a second
> > report
> > , some of the parameters to the second report are DateTime values, when
my
> > Local Settings are setted to English (United States) the link works
fine,
> > but when I change my Local Settings to Spanish I get a Type Mismatch
> > message for this DateTime parameters. The "Language" property of both
> > reports are "Default", and when I execute by my self the second report
> > specifying each parameter with the correct locale datetime format it
works
> > fine.
> > Any idea?
> > Thanks
> >
> >
>|||What are parameters values that you pass to second report? What do you put
into Parameter Value cell of Parameters dialog?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
news:%23HlTA0AnEHA.3196@.TK2MSFTNGP10.phx.gbl...
> Thanks for your answer, but I think that is not the problem.
>
> Let me explain the problem again, I have a first report with two
> parameters,
> "Start Date" and "End Date" that are used when the report is executed to
> get
> some information from some DB for this time range, this information is
> showed in a table where the first column values are links to other report
> (not a subrerport), this second report also uses date range parameters and
> its values should be the same of the first report parameters, this means
> that also should be specified in the link.
>
> So when I click the link to open the second report and I have Spanish or
> other locale selected for my system regional options a type mismatch
> message
> is showed instead of the second report:
>
> "The value provided for the report parameter 'EndDate' is not valid for
> its
> type. (rsReportParameterTypeMismatch)"
>
> My intuition is that the problem is with the date format, the date format
> for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy' I
> think that the second report is trying to build its date time parameters
> with the English locale and here is where the exception is raised. E.g.
> set
> a value greater than 12 as month.
>
> When I execute the second report specifying the parameters values manually
> with the correct locale date format the report is showed without problems.
> When I see the "Language" property of both reports in design mode is set
> to
> default, I suppose that means that the report should works with the system
> locale settings and use the correct date formats.
>
> Thanks
> Mauricio
>
> "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
>> this could happend because of session/caching of the subreport.
>> Click "Refresh" button on the toolbar when viewing the subreport.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
>> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
>> > Hi
>> > I have a report with a "Jump to report" navigation field to a second
>> > report
>> > , some of the parameters to the second report are DateTime values, when
> my
>> > Local Settings are setted to English (United States) the link works
> fine,
>> > but when I change my Local Settings to Spanish I get a Type Mismatch
>> > message for this DateTime parameters. The "Language" property of both
>> > reports are "Default", and when I execute by my self the second report
>> > specifying each parameter with the correct locale datetime format it
> works
>> > fine.
>> > Any idea?
>> > Thanks
>> >
>> >
>>
>|||The same values of the first report parameters:
Parameter Name Parameter Value
StartDate =Parameters!StartDate.Value
EndDate =Parameters!EndDate.Value
"Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
news:%23uc293FnEHA.3452@.TK2MSFTNGP15.phx.gbl...
> What are parameters values that you pass to second report? What do you put
> into Parameter Value cell of Parameters dialog?
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> news:%23HlTA0AnEHA.3196@.TK2MSFTNGP10.phx.gbl...
> > Thanks for your answer, but I think that is not the problem.
> >
> >
> >
> > Let me explain the problem again, I have a first report with two
> > parameters,
> > "Start Date" and "End Date" that are used when the report is executed to
> > get
> > some information from some DB for this time range, this information is
> > showed in a table where the first column values are links to other
report
> > (not a subrerport), this second report also uses date range parameters
and
> > its values should be the same of the first report parameters, this means
> > that also should be specified in the link.
> >
> >
> >
> > So when I click the link to open the second report and I have Spanish or
> > other locale selected for my system regional options a type mismatch
> > message
> > is showed instead of the second report:
> >
> >
> >
> > "The value provided for the report parameter 'EndDate' is not valid for
> > its
> > type. (rsReportParameterTypeMismatch)"
> >
> >
> >
> > My intuition is that the problem is with the date format, the date
format
> > for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy'
I
> > think that the second report is trying to build its date time parameters
> > with the English locale and here is where the exception is raised. E.g.
> > set
> > a value greater than 12 as month.
> >
> >
> >
> > When I execute the second report specifying the parameters values
manually
> > with the correct locale date format the report is showed without
problems.
> > When I see the "Language" property of both reports in design mode is set
> > to
> > default, I suppose that means that the report should works with the
system
> > locale settings and use the correct date formats.
> >
> >
> >
> > Thanks
> >
> > Mauricio
> >
> >
> >
> > "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> > news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
> >> this could happend because of session/caching of the subreport.
> >> Click "Refresh" button on the toolbar when viewing the subreport.
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >>
> >> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> >> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> >> > Hi
> >> > I have a report with a "Jump to report" navigation field to a second
> >> > report
> >> > , some of the parameters to the second report are DateTime values,
when
> > my
> >> > Local Settings are setted to English (United States) the link works
> > fine,
> >> > but when I change my Local Settings to Spanish I get a Type Mismatch
> >> > message for this DateTime parameters. The "Language" property of both
> >> > reports are "Default", and when I execute by my self the second
report
> >> > specifying each parameter with the correct locale datetime format it
> > works
> >> > fine.
> >> > Any idea?
> >> > Thanks
> >> >
> >> >
> >>
> >>
> >
> >
>|||I have having the very same problem. Did you ever solve this? And how
if you did?!
Thanks|||I have this problem as well, even though my report language is set to English
(United Kingdom), my Asp.Net app that calls the reporting service web service
is using en-GB as culture. It still thinks that my parameter End Date should
be in mm/dd/yyyy format and pukes when it sees something like 14/12/2004
(December 14, 2004) come over.
"Gearoid" wrote:
> I have having the very same problem. Did you ever solve this? And how
> if you did?!
> Thanks
>|||Adam,
Check the "Language Settings" for your browser.
Open IE, goto Tools->Internet Options->Click 'Languages...' button on the
General tab. Check that your language is English (United Kingdom)
I have got MSRS to work fine with UK English format dates... apart from
when reports are linked using 'Jump to' action.
Joe
"AdamB" wrote:
> I have this problem as well, even though my report language is set to English
> (United Kingdom), my Asp.Net app that calls the reporting service web service
> is using en-GB as culture. It still thinks that my parameter End Date should
> be in mm/dd/yyyy format and pukes when it sees something like 14/12/2004
> (December 14, 2004) come over.
> "Gearoid" wrote:
> > I have having the very same problem. Did you ever solve this? And how
> > if you did?!
> >
> > Thanks
> >
> >|||Try this and see if it works
Parameter Name Parameter Value
StartDate =Format(Parameters!StartDate.Value,
"dd-MMMM-yyyy")
EndDate =Format(Parameters!EndDate.Value,
"dd-MMMM-yyyy")
Cheers,
Harry
"Mauricio Cadima" wrote:
> The same values of the first report parameters:
> Parameter Name Parameter Value
> StartDate =Parameters!StartDate.Value
> EndDate =Parameters!EndDate.Value
> "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> news:%23uc293FnEHA.3452@.TK2MSFTNGP15.phx.gbl...
> > What are parameters values that you pass to second report? What do you put
> > into Parameter Value cell of Parameters dialog?
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> > news:%23HlTA0AnEHA.3196@.TK2MSFTNGP10.phx.gbl...
> > > Thanks for your answer, but I think that is not the problem.
> > >
> > >
> > >
> > > Let me explain the problem again, I have a first report with two
> > > parameters,
> > > "Start Date" and "End Date" that are used when the report is executed to
> > > get
> > > some information from some DB for this time range, this information is
> > > showed in a table where the first column values are links to other
> report
> > > (not a subrerport), this second report also uses date range parameters
> and
> > > its values should be the same of the first report parameters, this means
> > > that also should be specified in the link.
> > >
> > >
> > >
> > > So when I click the link to open the second report and I have Spanish or
> > > other locale selected for my system regional options a type mismatch
> > > message
> > > is showed instead of the second report:
> > >
> > >
> > >
> > > "The value provided for the report parameter 'EndDate' is not valid for
> > > its
> > > type. (rsReportParameterTypeMismatch)"
> > >
> > >
> > >
> > > My intuition is that the problem is with the date format, the date
> format
> > > for Spanish locales is 'dd/mm/yyyy' and for english locale 'mm/dd/yyyy'
> I
> > > think that the second report is trying to build its date time parameters
> > > with the English locale and here is where the exception is raised. E.g.
> > > set
> > > a value greater than 12 as month.
> > >
> > >
> > >
> > > When I execute the second report specifying the parameters values
> manually
> > > with the correct locale date format the report is showed without
> problems.
> > > When I see the "Language" property of both reports in design mode is set
> > > to
> > > default, I suppose that means that the report should works with the
> system
> > > locale settings and use the correct date formats.
> > >
> > >
> > >
> > > Thanks
> > >
> > > Mauricio
> > >
> > >
> > >
> > > "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> > > news:e8ju$c4mEHA.648@.tk2msftngp13.phx.gbl...
> > >> this could happend because of session/caching of the subreport.
> > >> Click "Refresh" button on the toolbar when viewing the subreport.
> > >>
> > >> --
> > >> This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > >>
> > >>
> > >> "Mauricio Cadima" <mcadima@.jalasoft.com> wrote in message
> > >> news:uqK6c$2mEHA.404@.TK2MSFTNGP12.phx.gbl...
> > >> > Hi
> > >> > I have a report with a "Jump to report" navigation field to a second
> > >> > report
> > >> > , some of the parameters to the second report are DateTime values,
> when
> > > my
> > >> > Local Settings are setted to English (United States) the link works
> > > fine,
> > >> > but when I change my Local Settings to Spanish I get a Type Mismatch
> > >> > message for this DateTime parameters. The "Language" property of both
> > >> > reports are "Default", and when I execute by my self the second
> report
> > >> > specifying each parameter with the correct locale datetime format it
> > > works
> > >> > fine.
> > >> > Any idea?
> > >> > Thanks
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> >
> >
>
>

Friday, February 24, 2012

Local Drillthrough Report 'Data source Instance has not been supplied'

I've searched and searched and can't find how to do this.
I've got a main report and a report that I am trying to use the 'Jump
to' ability with. I am capturing the ReportViewer1.DrillThrough event
and am doing this:
ReportViewer1.LocalReport.DataSources.Add(New
ReportDataSource("JobApplications_ApplicantDetails",
LoadApplicantDetailsData()))
I have set this report as the 'main' report that runs in the viewer
when it first loads and it works correctly but just not when 'jumped
to'. I have removed all parameters that need to be passed to the
report so there is nothing missing there.
This is the actual error I recieve:
A data source instance has not been supplied for the data source
'JobApplications_ApplicantDetails'.
Any help is greatly appreciated.
ThanksDo you still have these problems by viewing a new report in the same
reportviewer control after you activate a "jump to report" in the original
report (Me too...)
I will try to experiment more with it this evening.
Do somebody already have an answer
--
Regards
dagha
"hurst.andy@.gmail.com" wrote:
> I've searched and searched and can't find how to do this.
> I've got a main report and a report that I am trying to use the 'Jump
> to' ability with. I am capturing the ReportViewer1.DrillThrough event
> and am doing this:
> ReportViewer1.LocalReport.DataSources.Add(New
> ReportDataSource("JobApplications_ApplicantDetails",
> LoadApplicantDetailsData()))
> I have set this report as the 'main' report that runs in the viewer
> when it first loads and it works correctly but just not when 'jumped
> to'. I have removed all parameters that need to be passed to the
> report so there is nothing missing there.
> This is the actual error I recieve:
> A data source instance has not been supplied for the data source
> 'JobApplications_ApplicantDetails'.
> Any help is greatly appreciated.
> Thanks
>|||Hi I am getting the following error message when using drillthrough and
jump to another report in the same reportviewer.
Error message:
A Datasource instance has not been supplied for the data source
'DataSetProductDetail_ShowProductByProductID'
--
MyCode:
Protected Sub DemoDrillthroughEventHandler(ByVal sender As Object,
ByVal e As DrillthroughEventArgs) Handles ReportViewer1.Drillthrough
Dim drillthroughReport As LocalReport = CType(e.Report, LocalReport)
Dim MydataSet As DataSet = New DataSet()
Dim thisConnection As SqlConnection = New
SqlConnection(ConfigurationManager.ConnectionStrings("NorthwindConnectionString").ConnectionString)
Dim myCommandDataAdapter As SqlDataAdapter = New
SqlDataAdapter("DataSetProductDetail_ShowProductByProductID",
thisConnection)
myCommandDataAdapter.SelectCommand.CommandType =CommandType.StoredProcedure
myCommandDataAdapter.SelectCommand.CommandText ="ShowProductByProductID"
myCommandDataAdapter.SelectCommand.Parameters.Add(New
SqlParameter("@.ProductID", 2))
myCommandDataAdapter.Fill(MydataSet,
"DataSetProductDetail_ShowProductByProductID")
'Associate thisDataSet(now loaded with the stored procedure
result)
'with the ReportViewer datasource
Dim datasource1 As ReportDataSource = New
ReportDataSource("DataSetProductDetail_ShowProductByProductID",
Mydataset.Tables(0))
ReportViewer1.LocalReport.DataSources.Clear()
ReportViewer1.LocalReport.DataSources.Add(datasource1)
ReportViewer1.LocalReport.Refresh()
End Sub
--
Any ideas?
dagha wrote:
> Do you still have these problems by viewing a new report in the same
> reportviewer control after you activate a "jump to report" in the original
> report (Me too...)
> I will try to experiment more with it this evening.
> Do somebody already have an answer
> --
> Regards
> dagha
>
> "hurst.andy@.gmail.com" wrote:
> > I've searched and searched and can't find how to do this.
> >
> > I've got a main report and a report that I am trying to use the 'Jump
> > to' ability with. I am capturing the ReportViewer1.DrillThrough event
> > and am doing this:
> >
> > ReportViewer1.LocalReport.DataSources.Add(New
> > ReportDataSource("JobApplications_ApplicantDetails",
> > LoadApplicantDetailsData()))
> >
> > I have set this report as the 'main' report that runs in the viewer
> > when it first loads and it works correctly but just not when 'jumped
> > to'. I have removed all parameters that need to be passed to the
> > report so there is nothing missing there.
> >
> > This is the actual error I recieve:
> > A data source instance has not been supplied for the data source
> > 'JobApplications_ApplicantDetails'.
> >
> > Any help is greatly appreciated.
> > Thanks
> >
> >