Results 1 to 3 of 3

Thread: Opportunities and L10N

  1. #1
    Angel's Avatar
    Angel is offline Sugar Community Member
    Join Date
    Jul 2005
    Location
    Los Angeles
    Posts
    4,813

    Default Opportunities and L10N

    While attempting to help someone using the Spanish language pack, I came across an interesting situation.

    The matter at hand is that "closed" opportunities continue to display in the Opportunities listing. Upon inspection of the code in ListView.php and ListViewTop.php, I noticed that the where clause of the SQL select statement specifically omits Opportunities with the English terms 'Closed Won' and 'Closed Lost.' This works fine as long as you are using those terms for 'Closed' opportunities, but you wouldn't be if you were using a different language.

    Unless I've overlooked something (please help point me in the right direction if so), it seems as though I would need to modify the WHERE clause code in ListView.php and ListViewTop.php to the 'Closed' equivalent in Spanish in order to get it to behave properly.

    This, however, seems rather restrictive, since now users utilizing the English lang pack against the same Sugar database will malfunction.

    I would propose that rather than using the literal terms for determining if an opportunity is closed, Sugar's internals should be modified so as to include a value of 1 or 0 for each opportunity which in turn translates to whether or not the opportunity is open. Secondly, an array of values that would equal to 1 (closed) should be defined within the lang.php file. Lastly, the ListView.php and ListViewTop.php WHERE clauses should exclude those with a value of '0.'

    If I overlooked something that would solve the problem, I'd appreciate some input, in which case, disregard my proposal above.
    Regards,

    Angel Magaņa
    Co-Author: Implementing SugarCRM 5.x (Packt Publishing -- Sept. 2010)
    Blog: http://cheleguanaco.blogspot.com.
    Twitter: @cheleguanaco.

    ________
    | Projects: |_____________________________________
    |
    | CandyWrapper (.NET Wrapper for SugarCRM SOAP API). Source now available on GitHub!
    | GoldMine to SugarCRM Express Conversion. Latest: 1.0.1.7 (Nov. 3, 2009)
    | CRM SkyDialer (Skype Integration). Latest: 1.0.2 (Feb. 17, 2010)
    | Round Robin Leads Assignment
    | Phone Number Formatter
    | CaseTwit (Twitter Integration)
    ______________________________________________

  2. #2
    ruchida's Avatar
    ruchida is offline A Sugar Hero | Help Forum Moderator
    Join Date
    Feb 2005
    Location
    Japan
    Posts
    1,375

    Default Re: Opportunities and L10N

    Angel,

    Good point.

    I think this has been a long time deficit of Opputinities and Dashboards as well, but I'm not sure if someone already submitted a bug for this.

    Would you please file a bug for this? Now you can file it for the product category - "I18N & L10N".
    Ryuhei Uchida
    Help Forum Moderator
    Calendar 2.0
    http://blogs.itmedia.co.jp/ruchida/

  3. #3
    julian's Avatar
    julian is offline Sugar Team Member
    Join Date
    Sep 2004
    Posts
    1,639

    Default Re: Opportunities and L10N

    Hello,

    Sugar uses the English "keys" in the database, throughout the entire application. Therefore, even if you're using the Spanish language pack, the same keys will be used to communicate with the database.

    Have you specifically been able to reproduce this behavior, where closed Opportunities are displayed when using Spanish, but not in English? Thanks,
    Julian Ostrow
    Systems and Applications Engineer
    SugarCRM Inc.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •