Records aren't viewable

Hello,
I recently updated from 7 to 8. Currently on 8.5.0. The old install was on a shared server with restricted permissions, so there were issues getting things to work. I installed 8 on a stand alone server so we could get around the permissions issues. When I created the modules, and loaded in exported data from the old system, I can not click on any of the records. When you click on the module, and click view, the list view populates with all the records that I imported, but there is no link or button to view the actual record. The list view is the only view that I have of the records. Additionally, when I create a new record in the same module, it displays the same way. I have no way to load the record and look at it.

I seem to remember back from the version 7 system, there was an option in Studio to say that this field was a link, but I can’t find that anymore. Adding the link=true into the code doesn’t work either.

What am I missing? I feel like it’s something silly.

Thank you in advance!

I’ve created 2 custom modules.

Hello Peter,

usually, there is a system required field - often the name - which is the link to the detail view.

If you check your list view (or your studio) do you have this field visible in your list view?

And you’re currently using the admin account for checking the system, right?
It is possible to do exactly what you described via the roles + permissions.

In what module are you? Can you try this in a standard module like leads or similar?

Do you have any customizations / custom code or only those two modules?

Hi Bastian,
Thanks for your response. When I created the module(s) it did come with a name field, but I had no real use for it. When I imported the data from the old CRM, I put useless data into those fields because I knew I wasn’t going to display it on the list view. Because it was required, I had to put something in there when I imported the data. After reading your post, I went back, and added the name field to the list view, and bingo, there’s the link. It’s got useless information, but it does open the correct record.

First, and foremost, thank you for this. But this brings up several other questions if you don’t mind.

  1. Does the name field have to be the linked field? Can I set a different label or field to be the linked field to open the record? I seem to remember an option in earlier versions of Suite where there was a checkbox for ā€œis a linkā€ or something along those lines.
  2. If I can’t make another field a link, Can I rename the label without it affecting the linking operation? I know the field will stay the same, but if I was to change the label to ā€œInspection Numberā€ or something like that, would that affect the operation?

Can you go into a little more depth regarding roles and permissions? I’m not sure what you’re referring to as ā€œI can do exactly that with roles + permissionsā€. I haven’t gone that deep yet, and there’s only a small number of people using the system I’m creating. Currently 2, will likely grow to 4 or 5 eventually. I didn’t think it would be necessary to set those up with such a small user base.

Thank you again for your reply and help!

If I am not wrong, then you can just change the label as per your requirement and use it as link field. Check the metadata/listviewdefs.php code.


Checkout the below doc about roles:

and this video:

Hi RSP,
Thank you for this. I don’t think it’s currently necessary for me based on our usage, but now I understand what Bastian was referring to. He wanted to make sure that there wasn’t a security group rule preventing the access or display. In the future, I do see a use for this as we are expanding geographically, and I could see a use for the North and South example this presenter offered.

Also, good to know about changing the label. I think I’d like to use that as a Plan B if I don’t have the option to add a link mechanism to the field I created.

Thank you again!

Are you using v8.5? Is there any plan to upgrade to v8.8?

We are on 8.5 now. No plans to upgrade, but I’m also not opposed if there is an immediate benefit?

Yeah, no need to hurry. :face_with_peeking_eye:

But, I think v8.8 added new features, resolved bugs and improved the UI. :star_struck:

Hi Peter,

there have been several vulnerability fixes in the 8.7 8.7 Releases :: SuiteCRM Documentation
and of course, the much improved UI in 8.8 :slight_smile: , check out my video:

As for the label: Sometimes I use the name label as an important one, and just rename it.
For example, the lead module has a ā€˜name’ field - the last name.
So you can check your module, whether you’ve got a text field which is usually filled, and just use the name field for that purpose and rename the label.

With the URL field you can generate a link - even one to the current record, but you’d replicate standard features.
Then I’d rather go with custom code like rsp suggested, if you really have to.
But usually, I first try to move a purpose of a text field to the system required name text field (like the last name example) if possible.

1 Like