Wednesday, November 19, 2008 ..:: Forums ::.. Register  Login
 Forums Minimize
SearchForum Home
     
  Mainstream Forums  General Discussion  Report adn Drop...
 Re: Report adn DropDown
 
sarah
47 posts
Joined
9/14/2007

Re: Report adn DropDown
Posted: 29 Sep 07 9:13 AM
I've the same problem.... Can you tell me when It will be  fixed??
support
2089 posts
1st
Joined
1/3/2006

Re: Report adn DropDown
Posted: 29 Sep 07 10:25 AM

No.  We have a lot of things on our plate and this issue is not something that can be fixed quickly.

 

sarah
47 posts
Joined
9/14/2007

Re: Report adn DropDown
Posted: 29 Sep 07 4:17 PM
Can you tell me how Can I try to resolve it?
support
2089 posts
1st
Joined
1/3/2006

Re: Report adn DropDown
Posted: 29 Sep 07 5:40 PM

Take a look at ~/Projects/ProjectTsk.ascx.cs.  After we select the data, we localize the STATUS field for every row in the table.

foreach(DataRow row in dt.Rows)
{
   row[
"STATUS"] = L10n.Term(".project_task_status_options.", row["STATUS"]);
}

You have to do the same thing in the reports, but you need to make sure to localize any and all fields that need to be localized. 

There are two tough issues here: 1) you need to determine the fields in the report that need to localized, and 2) you need to determine what list name to use when localizing the fields.

 

 

sarah
47 posts
Joined
9/14/2007

Re: Report adn DropDown
Posted: 07 Oct 07 5:54 PM
Thanks for help me!! But I don't know the name of the file to modify.... if I want to fix this problem in the reports... where Can I find the files/file to modify?

Thanks!!!!!
  Mainstream Forums  General Discussion  Report adn Drop...

Forum Home  Search       

Copyright (c) 2006-2008 SplendidCRM Software, Inc. All Rights Reserved.   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2008 by Perpetual Motion Interactive Systems Inc.
SplendidCRM and SplendidCRM Software are trademarks of SplendidCRM Software, Inc. SugarCRM is a trademark of SugarCRM Inc. in the United States, the European Union and other countries. All other trademarks used in this web site are the property of their respective owners.