Details about this thread
  • State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 314 subscribers
  • Views 898 views
  • Users 0 members are here
Related content from around SugarClub

Default Value

Joey Maguliman

Hello!


I created dependency formulas in the Calls Module, to which a radio-button will only pop up if a certain field is selected (if Intent is Sales, then a radio-button pops up). I initially had it defaulted to one of the options in the radio field. However, when I pulled a report, the default option is showing, even Sales was not chosen from the drop-down.

Anyone know how to resolve this? Or suggestions?

  • 0

    Hi Joey,

    I had the same problem - the solution was to have a blank as the default.

    To clean up my mess, I was opening each record - changing the selection for the parent field, changing the selection to the blank, changing it back to the parent choice, then saving the record again.

    If you have the Import set for that field, you could export the affected records, make the field blank and then import them with the "update records" option selected. I did that in another module that had hundreds of records with the default set in an unrelated field.

    Be careful!  If you have a process running for that field you make "break" things in process.

    Bud Hartley | Cape Foulwind, NZ (and Oregon, USA)

  • 0 in reply to Bud Hartley

    As  said, allow a default blank. When you deploy a field all the existing records will get the default value if there is one, regardless of dependencies which are really a front-end mechanism.


    If your deployment is On Site and you have direct DB access you can use SQL to set the value to Null if the Intent is not Sales. It's what I would do, but we are an on Site deployment with direct access to the database.

    If you are on Cloud, you could script something similar and run it as a one-off scheduler: Loop through all the beans for that module where the intent is not Sales set the radio field to null for each of them (You can fetch them with a SugarQuery)
    Or, perhaps, you could ask Support to run the SQL fix for you on the DB side.

    FrancescaS

  • 0 in reply to Francesca Shiekh

    What a bummer. Thank you both for the response!

    I opted to not use a default option in this case, and made the field required instead.