Localizing Time

Does Reporting Services provide any facilities for localizing DateTime
values based on the location of the server itself? We have DateTime values
stored in the database, and need them displayed converted to local time
where the server is located.
Thanks,
JasYou have access to all of the date/time manipulation functions of VB.Net
(http://msdn.microsoft.com/library/en-us/cpref/html/frlrfSystemDateTimeClass
Topic.asp) so you should be able to do whatever conversions are appropriate
for your application.
--
This post is provided 'AS IS' with no warranties, and confers no rights. All
rights reserved. Some assembly required. Batteries not included. Your
mileage may vary. Objects in mirror may be closer than they appear. No user
serviceable parts inside. Opening cover voids warranty. Keep out of reach of
children under 3.
"J Smith" <rs-nntp@.jascentral.com> wrote in message
news:ePM9MzGkEHA.3160@.TK2MSFTNGP10.phx.gbl...
> Does Reporting Services provide any facilities for localizing DateTime
> values based on the location of the server itself? We have DateTime
values
> stored in the database, and need them displayed converted to local time
> where the server is located.
> Thanks,
> Jas
>

Localizing Labels

Hi,

I am working on localizing SSRS reports and wanted to store the text for the labels in the database for different languages. The Language id would be passed by the user as a parameter. Based on this Language ID, the required data for the labels would be fetched and stored in a dataset in the custom code. This dataset would then be searched for relevant LabelIDs and the label caption in the particular language would be returned. The dataset would be a shared variable so it would get initialized the first time. For initializing the dataset I would need the datasource information, which would either be stored in the Shared Data source or embedded in the Report.

Can I refer to the shared data source being used by the current report in the Custom Code Window ? Or can I retrieve the data source information embedded in the report and use it in the Custom Code? If so, how ?

Thanks In Advance.

Ashish

Hi Guys,

Does any one know as to how can we access the data source connection information from Custom Code ?

I need that information to populate a custom dataset created in the Custom Code.

Please help.

TIA.

Ashish

Localizing cube elements

We're an ISV that builds a product which includes a predefined set of SSAS2005 cubes, dimensions, and measures. We want to support the localization of the various cube elements. The ideal way would be to use translations - however, we need to support Standard Edition, and my understanding is that translations are only supported under Enterprise Edition. :( So the question is, what's the best way to accomplish this and still support SE?

Right now we're looking at using AMO to programmatically translate the various OLAP elements (we also looked at directly modifying the XML/A deployment script, but aren't pursuing that option for process reasons). There are some concerns about this approach, however. There doesn't seem to be a language-independent way to identify specific OLAP objects from an OLAP client (there is an ID property on some objects, but as far as I can tell it isn't usable from ADOMD.NET, and it isn't present on all objects anyway). In other words, in our admin tools if we want to query a specific cube, there's no language independent way to reference it.

Also, if we change the names of, for example, a measure, we also need to change the expression for any calculations that reference that measure.

Is there some more elegant solution that we're missing here?

Thanks,
Kevin

Kevin.

You can argue back and fourth but looks like the answer for your case is to use translations :).
And that is the feature desinged specifically for the case you describe.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Oh, I agree - which is why I was extremely disappointed when translations was announced as an enterprise edition feature only. That decision really complicated the lives of ISVs. A nice compromise might have been to support a single translation on SE, so that ISVs could localize to one foreign language without having to rename all of their cube elements.

Anyway, it sounds like you're saying that isn't much of a good alternative here that supports SE.

Localization of Reports

Are there any plans to improve the process of localizing reports? for example, it would be nice to extend the RDL schema to include a section for resource strings and localization information.

Thanks

This is very high on our wish list. Unfortunately, it will most likely not make it in Katmai.

|||

Hi Brian,

Sorry to hear that we won't see this functionality in Katmai. Should we start a campaign and try to get it into Katmai J?

Given we have to deal with this reality for a while, what is the best approach to localize reports. We know about the recommendation in http://msdn2.microsoft.com/en-us/library/ms156493.aspx and http://technet.microsoft.com/en-us/library/aa964130.aspx.

We have 100’s of reports and we don’t want to make sacrifice performance, if possible.

Thanks