Dependent visibility of fields with reference to related data records

Hi community,

we have the following problem: We are experiencing this behavior and Sugar is apparently not planning a fix: https://portal.sugarondemand.com/#supp_Bugs/89857

The behavior described there does not have to be an HTML field. A simple checkbox or a dropdown also have a similar behavior.

Are there any members here who have already created a workaround? It is very frustrating that even in 14.2 dependent fields with a reference to a parent module simply disappear in certain constellations, although they should be displayed and you can only display this again by refreshing the page The faulty behavior also runs through the record dashlet.

I would be pleased to receive suggestions or workarounds.

Many thanks in advance.

Best Regards

Axel

  • Hi  ,

    Interestingly, I cannot reproduce that exact bug as it is written, but I have seen what you described with checkboxes and related module dependencies. I recently filed a bug that is very similar in nature and the root cause is most likely the same:

    https://portal.sugarondemand.com/#supp_Bugs/95999

    The bug centers around Sugar views not consistently returning all field values required to properly render the view and dependent functions. My particular issue was with Action Buttons using calculations when the fields involved in the calculation are not all on record view. The workaround (though not great) for that issue was to place the fields on the record view. I think your use case highlights a scenario where the workaround isn't applicable at all since you can't place the related module fields on the view.

    In the scenario I can reproduce similar to yours, I had a checkbox on Opportunities that was dependent on the related account's industry. The checkbox would always show after saving the opportunity. If I added a text field that was calculated and pulled the account industry value (to try and apply the workaround for your scenario), then the checkbox was always hidden after saving the opportunity. I wish I had a suggestion on how you could work around this issue that would apply to all the various views.

    If you think my bug applies, I recommend requesting your case be attached to it by Sugar Support. The root cause of this issue has probably cropped up in a few different ways that doesn't make it easily apparent they are actually related. 

    Chris

  • I noticed something vaguely similar with using Module Builder and Studio in v14.0 today.

    I did not take exact notes to reproduce but basically the display of the page is not re-rendered after the Save action.

    I rearranged some fields in Module Builder, saved, and the Builder showed no changes after the Save. I reloaded the page and my changes were there.

    Similarly I added a relationship, after deploying the new module, and after saving it wasn't in the list of relationships.
    At first I thought I made a mistake so I tried adding the relationship again and nothing. I reloaded the page and I had two!

    I can't be certain but all these things seem to lead to an issue (maybe a timing issue?) with re-rendering the page we are on when certain data changes?

    Francesca