Bulk update values in drop down editor

Hi Everyone,

I am looking for a solution where we have a drop down in opportunities for the amount of users.

We want to import around 250+ different values into this drop down but I am not seeing any import options only manually adding each value one at a time.

We are currently using a drop down field which is sub-optimal but we are wanting to change to a lookup field.

Does anyone know a better solution to doing this or any recommendations in to how I would proceed?

Thanks in advance,

Sam

  • Hi  ,

    The Easy option is to create New custom module and import all the values as record in that custom module. Then Create relationship with the module where you need this field.

    Hope this will help you.

    Regards,

    BPATEL

  • Dropdown values are stored in the file system in: 

    custom/Extension/application/Ext/Language/

    The file format is <language prefix>.sugar_<dropdown_list_name>.php

    For example: 

    custom/Extension/application/Ext/Language/en_us.sugar_call_status_dom.php

    the file then contains the list as "key=>label" pairs

    for example:

    <?php
     // created: 2015-12-31 08:49:15
    
    $app_list_strings['call_status_dom']=array (
      'Planned' => 'Planned',
      'Held' => 'Completed',
      'Not Held' => 'Canceled',
    );

    So you could easily generate the file and upload it to your system (I do that on my  OnSite instance when copying modifications from TST to PRD). I would think you should be able to include the file in a manifest to deploy to a cloud instance.

    If you are in Cloud you should be able to get a backup of your instance, get the original list, edit it, and re-upload it with the right manifest.

    Having said that, I would question the business logic behind this choice.

    A 250+ value dropdown is very hard to scroll through and not very user-friendly.

    FrancescaS

  • For your use case, why not use an integer field instead, is there a reason not to?

  • This is a possible solution if I was able to only pick in blocks of 25 as there was an issue before where anyone was selecting any sort of number skewing the data as we only sold licenses to 25, 50, 75, 100 etc...


    Thanks everyone else for the helpful recommendations.

  • hi  

    To restrict the input based on that criteria I believe your best options are either the Custom module as previously suggested by  or alternatively an integer field controlled by custom code that only allows numbers divisible by 25

    .

    CRM Business Consultant

  • why not use Two fields:

     - an integer field for the number of blocks they want to buy,

     - a calculated integer field for quantity that is the number of blocks entered multiplied by 25.

    So if I enter 1 for the number of blocks I get quantity 25,

    If I enter 9 I get a quantity of 225 etc...

    FrancescaS

  • Hi  ,

    You can ensure an integer field is in a certain increment using a supporting Sugar Logic field. I was able to accomplish this with a custom text field that is both required and calculated. The calculation will only populate a value into the field if purchased licenses is in an increment of 25. In other words, the user would not be able to save the record until they put in a proper license count since the field is required:

    Sugar Logic does not have a remainder function, so you need to work around that by manually evaluating for a remainder. Here is the formula I used:

    ifElse(
        equal(
            subtract(
                multiply(
                    25,
                    round(
                        divide(
                            $licenses_sold_c, 
                            25
                        ),
                        0
                    )
                ),
                $licenses_sold_c
            ),
            0
        ),
        "Yes",
        ""
    )

    So, if the licenses sold is in an increment of 25, then the field will display 'Yes' and the record can be saved. For any other value, the field is empty and the record cannot be saved.

    The field needs to be added to the record view for this to work since required fields not on the record view will not be evaluated.

    I hope this helps!

    Chris