Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 352 subscribers
  • Views 474 views
  • Users 0 members are here
Forum Actions
Related

Dependency on dropdown value challenge

Lucy Smith

Hi

Hopefully a simple one. I'm creating a dependency based on a single value from a dropdown list. It's working to only show the field when the value is selected, however, it also shows when the value is blank. We have the dropdown set to default to blank.

isInList($bvdid_status_c,createList("BVDID_Does_Not_Exist",))

Can anyone advise how to ensure the field do not appear when the field is blank?

Best wishes

Lucy

  • 0

    I think the trailing comma inside your createList may be allowing the blank as a valid option :)

    Try changing

    isInList($bvdid_status_c,createList("BVDID_Does_Not_Exist",))

    to

    isInList($bvdid_status_c,createList("BVDID_Does_Not_Exist"))


    FrancescaS

  • 0

    Sorry to Hijack your question, but mine is very similar - If I want to make a field (actually multiple fields) only show if any one of a series of linked/related fields contain a value - (they will all have the same fieldname/relationship.) will that still work.

    Ie. if an Opportunity has a series of potential products linked - and one is currently selected, but the others are still in the list of products - and we were looking for any product with feature - X - to trigger questions about X - would that be the identical formula, or would we have to add some more code to allow for the possibility that one may be yes and another may be no?

    (I think I have just realised you can't have related fields anyway in a visibility formula?)

  • 0 in reply to Adam Ososki

    Hi  ,

    You should be able to use related fields in a visibility formula (assuming it is for a 1:1 for Many:1 relationship for the current:related module). However, there are bugs (88992 & 89335) with the field consistently showing in the view, so I do not recommend trying it until those bugs are solved.

    The best thing to do is to find a way (SugarBPM or custom logic hook) to set a value in a hidden field on your target module when a record meeting your desired conditions is related or a related record is updated to meet those conditions. Then you can base your visibility on that hidden field value.

    Chris 

    Co-Founder | SugarCRM's 2024 Global Outfitters Partner of the Year

  • 0 in reply to Chris Raffle

    Thanks Chris - we are on a highly developed version of 12.05 Enterprise. I need to avoid dev and only do things I can do simply in Studio with calculated fields or drop down dependencies. When I go into the formula area for visibility it doesn't have the "related field" option at the top. Maybe it's possible if I directly enter the correct formula including the related field that it will pick it up.  ( I am just a user so I don't have access to read those bugs)