Contracts related subpanel in Sugar mobile not populating

Hi Christopher Hart, by your screenshot it looks like you might be using the mobile browser view accessed via the desktop app, which opens a browser version of the mobile app in your browser. Unfortunately, the browser version is not the same as the actual SugarCRM mobile app. I am having the same issue as you in the browser version but it works fine in the actual app on 13.0. Have you tried testing on the actual app?

-Brenda

Thanks for the feedback Brenda, it works on the app in V13 but not on a pure/OOTB verison of V12.0.x

Seems this was a bug a long time ago, fixed in SugarCRM Mobile App 47.0
https://support.sugarcrm.com/documentation/mobile_solutions/sugarcrm_mobile/sugarcrm_mobile_app_release_notes/sugarcrm_mobile_app_archived_release_notes/#Fixed_Issues_14

• 88610: The Contracts subpanel may not be displayed in the Related tab of modules with a relationship to contracts (e.g., accounts)

Suggest raising a support Case

Great find, Tony Romano! You are right, the issue was fixed in version 47.0 of the mobile app. However, I looked into it further and it also depends on the version of Sugar that you are connected to. You need to be connected to Sugar 12.2+ for the issue to be fully addressed, so unfortunately it would still be reproducible if connected to Sugar 12.0. This is why you're still seeing it when using 12.0 but not 13.0, Christopher Hart.

-Brenda

hi Brenda Rossetto 

I'm confused. When Mobile v47.0 was released in July 20202 it was compatible with recently released Sugar v12.0 (19 April 2022).

Apart from that, it was a recognized bug, therefore if fixed in v12.2 then would also have been fixed in one of the later Enterprise v12.x versions 

Would be really appreciated if the flaw in my reasoning can be clarified.

Thank you in advance.

hi Brenda Rossetto 

I'm confused. When Mobile v47.0 was released in July 20202 it was compatible with recently released Sugar v12.0 (19 April 2022).

Apart from that, it was a recognized bug, therefore if fixed in v12.2 then would also have been fixed in one of the later Enterprise v12.x versions 

Would be really appreciated if the flaw in my reasoning can be clarified.

Thank you in advance.

It's a fair point. In this case, the root cause was an issue on the Sugar side with how Sugar passes information to the mobile app, which manifested as an issue on the mobile side. So, while the actual fix, or at least part of it, was applied in Sugar 12.2, it was treated as a fixed issue in the release notes for the mobile product because that is where users encounter it. There may have also been a change made in the mobile app in version 47.0 to fully address the issue, but I'm not aware of the specifics myself.

These sorts of situations don't happen all that often, but they do arise once in a while with our interdependent products like this. I can see the value in putting a fixed issue like this in the Sugar release notes (i.e., in 12.2 in this case) also, to help people impacted by it to pinpoint the Sugar version they need to be connected to to see it fully resolved. I'll take this back to the team and see if it makes sense to refine the approach for these dependency situations. Thank you for bringing it up!

-Brenda

Thank you Brenda Rossetto for progressing this issue, especially why the fix wasn't applied within Enterprise v12.0.2 or other v12.x please?

At the same time can you confirm if support can do the usual and provide a patch

Thank you in advance.

Hi Tony, I won't be able to help in that regard, but if this issue is impacting you in 12.0.x, I would submit a case to Support so that Sugar can keep track of the extent of people affected by this particular issue and see if there's anything we can do to help. In the meantime, I'm going to take another look at how we represent cross-product fixed issues in the release notes to see if we can provide more clarity on these types of situations in the future.

Thanks!

-Brenda

Hi Brenda, I raised a case with Sugar support and they provided a patch which I have included here for reference.

I don't think the link you provided will work for anyone else, but the hotfix may not work across the board for everyone anyway, depending on product and version, etc.

But, anyone interested in getting a hotfix for their own instance can absolutely submit a case to Support to get one.

I'm glad you got what you needed though, Christopher Hart!