Data Not Available Message on Accessing Modules in SugarCRM

Hi Everyone,

We are facing a issue when accessing some of the modules in Sugar Instance. When we are trying to view records in the specific module it throws up "Data not available, Page does not exists or you do not have permissions to access this page" message as shown in screenshot below. I have tried using different license types and with different users like admin and regular. We are facing this issue this kind of issue in 3-4 instances and few users are able to access the modules data fine. I am just wondering is this related to license key( if we use more users than what we are supposed to) or something else? Can someone suggest me why this is happening and how to fix this kind of issues. 

Parents
  • Could you share a little more about which users it works for?

    Specifically, if a user is admin, do they ever have any problems? If not, then it is as John has said, and it'll relate to the security permissions configured for the non-admin users who trying to access the record. Do you use Teams in your implementation?

    If this isn't by design, these are some common reasons it occurs inadvertently:

    • Users have been taken out of the Global team - meaning they can't see the same records as everyone else.
    • A user has changed the "default teams" setting, which means that records they create have a different security profile (e.g. those records may belong to a specific team which not everyone is a member of).
  • Hi Everyone, 

    To answer for everyone we have not configured any roles or team restrictions on any Instances where we are facing the issues. We are getting this issue even for admin user. 

  • Hi Adam,

    Thanks for your inputs. We have tried all the scenarios you have mentioned. It is happening for admin users and also regular users. But not for all and all the time. We have just implemented the instance and renamed the stock modules, created data. To be very clear no role and team based restrictions. All the records are under global only. It is happening not only in one instance for me, its occuring in the few other instances. I am just wondering is this something related to 10.x version.

Reply
  • Hi Adam,

    Thanks for your inputs. We have tried all the scenarios you have mentioned. It is happening for admin users and also regular users. But not for all and all the time. We have just implemented the instance and renamed the stock modules, created data. To be very clear no role and team based restrictions. All the records are under global only. It is happening not only in one instance for me, its occuring in the few other instances. I am just wondering is this something related to 10.x version.

Children
  • It is not related to 10.x version - I have been able to rename stock modules in a vanilla instance and not been able to reproduce the error you're seeing (and v10 has been out for several months now..)

    If you tried all the scenarios, can you please note what the results were? The goal was to use the answers from there to identify where the root cause was.

    re: your final comment on only renaming stock modules.. your screenshot has the following modules in it:

    • Companies (renamed Accounts?)
    • Investors (what stock module was this renamed from?)
    • Investment Banks (what stock module was this renamed from?)
    • Contacts
    • Leads
    • Opportunities
    • Deals (what stock module was this renamed from?)
    • Exits (what stock module was this renamed from?)
    • Shareholders (what stock module was this renamed from?)
    • Financial Performance (what stock module was this renamed from?)

    At least one of the above, I'm guessing, is not a renamed stock module - meaning your template does have some custom work in it.

    Are you accessing the record from a List View? Or if not there, then from where?

  • Hi Adam,

    Thanks for your Inputs. We have created all this custom modules from default templates available in Module Builder. And this issue is happening on custom modules developed when accessing the module itself. When we click on module in the Navigation Bar we are getting issue sometimes to specific user(both regular and admin). This issue is not only happening in one instance for me, I have been facing this issue in other instances where nothing was customised apart from creating data in default modules. So I am just wondering why this is happening in most of the instances. Could you please suggest how we can go to deep into issue. Thanks in Advance.

  • Hi  When the error happens, can you take a screenshot of the chrome network tab and console and share it here? Usually that will give more clues on whether this happened because of a failing backend api call or something else.