Data Not Available Message on Accessing Modules in SugarCRM

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 Poojitha,

Thank you for clarifying that.

Ramya Katram said:

fresh SugarCRM instances with only data. No customisation's are implemented

Just thinking over this and noting your screenshot has a few custom modules in it. It cannot be both a fresh instance, and have custom modules - implying perhaps you are creating from a template that your team has made. Is it possible there is an issue there? Is the screenshot from the custom module? Or from a core module? Is the issue reproducible in multiple modules? If so, are they all custom, all core, or a mix of custom and core?

If none of those questions help find an answer, can you please check / confirm the following:

• The admin user gets the issue for the same record in a reproducible fashion?
• It's the same record that other users face the issue on (and its also reproducible?)
• There are some users who do not face this issue - and if they visit this same record, they consistently are able to see the record.
• For the users (both admin and non-admin) that have issues seeing this record - there are other records in the same module which they can see.

If those are all correct, can you please try the following:

• If you duplicate the admin user and try visiting the record, what is the reproducible behaviour?
• If you create a brand new admin user with nothing but the minimum fields, what is the reproducible behaviour?
• If you duplicate the working non-admin user and try visiting the record, what is the reproducible behaviour?
• If you duplicate the non-working non-admin user and try visiting the record, what is the reproducible behaviour?
• If you create a brand new non-admin user with nothing but the minimum fields, what is the reproducible behaviour?
• If you duplicate the record (when logged in as a non-admin non-working user) which this unexpected behaviour, what happens when the above users try visiting it?
• If you duplicate the record (when logged in as a non-admin working user) which this unexpected behaviour, what happens when the above users try visiting it?

The goal of these tests are to identify if there's something about the records, or users, or default settings, which create the problem.

Hi Poojitha,

Thank you for clarifying that.

Ramya Katram said:

fresh SugarCRM instances with only data. No customisation's are implemented

Just thinking over this and noting your screenshot has a few custom modules in it. It cannot be both a fresh instance, and have custom modules - implying perhaps you are creating from a template that your team has made. Is it possible there is an issue there? Is the screenshot from the custom module? Or from a core module? Is the issue reproducible in multiple modules? If so, are they all custom, all core, or a mix of custom and core?

If none of those questions help find an answer, can you please check / confirm the following:

• The admin user gets the issue for the same record in a reproducible fashion?
• It's the same record that other users face the issue on (and its also reproducible?)
• There are some users who do not face this issue - and if they visit this same record, they consistently are able to see the record.
• For the users (both admin and non-admin) that have issues seeing this record - there are other records in the same module which they can see.

If those are all correct, can you please try the following:

• If you duplicate the admin user and try visiting the record, what is the reproducible behaviour?
• If you create a brand new admin user with nothing but the minimum fields, what is the reproducible behaviour?
• If you duplicate the working non-admin user and try visiting the record, what is the reproducible behaviour?
• If you duplicate the non-working non-admin user and try visiting the record, what is the reproducible behaviour?
• If you create a brand new non-admin user with nothing but the minimum fields, what is the reproducible behaviour?
• If you duplicate the record (when logged in as a non-admin non-working user) which this unexpected behaviour, what happens when the above users try visiting it?
• If you duplicate the record (when logged in as a non-admin working user) which this unexpected behaviour, what happens when the above users try visiting it?

The goal of these tests are to identify if there's something about the records, or users, or default settings, which create the problem.