pagination problems on v12

I am v12 Ent (working on it, I know I'm behind... again)

I have a pagination issue.

In Opportunities there is a Contacts subpanel.

When I load the opportunity if the subpanel is closed it shows 9 Contacts:

opening it shows 5 contacts of 6+ and the pagination button without a number of pages (which I believe is as expected)

Now I paginate to the next page, I am expecting page 2 with 4 contacts and a count of 6-9  of 9 contacts.
Instead it claims to show 11-13 of 9

Not only that, but it says it's page 2 of 1 and has scrolls both forward to the next page and back to the first page.

If from this second page I move forward  or  back 

I find myself back on page 1 with both forward and back buttons disabled and a count of page 1 of 1, yet still 9 contacts.

This seems to happen on Contacts subpanels in other modules as well, but I am not seeing the same problem in Leads subpanels, or quotes etc

All other subpanels show records 10 at at time, Contacts seems to be random.

On one account with 37 contacts I see

5 contacts on page 1,

4 contacts on page 2 (labeled 11 thorough 14 of 37)

8 contacts on page 4 (labeled 31 through 38 of 37

Any thoughts on how to debug this?

Thanks,
FrancescaS

Parents Reply Children
  • In v14.0.0 I removed everything but "Name" and tested adding the fields I had before one at a time.

    The Subpanel displayed correctly 10 entries at a time, paginating correctly for each added field except Email.

    When I added Email then the counts are off and the scrolling is broken.

    I wiped the entire subpanel from Accounts and rebuilt it in Studio and the problem came back with the addition of the Email:

    <?php
    // created: 2024-10-11 16:03:43
    $viewdefs['Contacts']['base']['view']['subpanel-for-accounts-contacts'] = array (
      'type' => 'subpanel-list',
      'panels' =>
      array (
        0 =>
        array (
          'name' => 'panel_header',
          'label' => 'LBL_PANEL_1',
          'fields' =>
          array (
            0 =>
            array (
              'name' => 'name',
              'type' => 'fullname',
              'fields' =>
              array (
                0 => 'salutation',
                1 => 'first_name',
                2 => 'last_name',
              ),
              'link' => true,
              'label' => 'LBL_LIST_NAME',
              'enabled' => true,
              'default' => true,
            ),
            1 =>
            array (
              'name' => 'email',
              'label' => 'LBL_LIST_EMAIL',
              'enabled' => true,
              'default' => true,
            ),
            2 =>
            array (
              'name' => 'phone_work',
              'label' => 'LBL_LIST_PHONE',
              'enabled' => true,
              'default' => true,
            ),
         

    Additional oddity: When updating the subpanel from Studio I had to add a field, save-and-deploy. And the field I just added would move back to the Hidden column. The second time I re-added it and save-and-deploy it would stick.

    I am going to dig through my customizations and see if we had changes to the email field at any point in time.

    Thank you,

    FrancescaS

  • Sounds great. 

    As I mentioned previously this is happening due to the relationship. SQL Returns some records but Distinct evaluation wipe some of them and log them aside. 

    At this moment, I could blindly guess, somehow an email would be use in multiple same records. You can check the IDs logged in the email addresses to see if it gives you more info. Moreover, the best could be log only the related api end point logs in the sugarcrm.log to get exact query. 

    Good luck on your investigations. 

    Let me know if you have any further questions.

    Tev.

  •   you hit the nail on the head!


    Multiple contacts related to the Account shared a corporate email address as the secondary address. Removing that address fixes the issue.

    So it seems that multiple Contacts on an Account CANNOT share an email address or things will get out of whack.

    This is going to be a problem for us since it's not an unusual case.

    I will be filing a case to see what the developer side of the house thinks.

    Note: I also had a problem with the denormalizaiton of Account Name on Contacts, given that our relationship is M-M since v6 the denorm was causing duplicated records (one per account name).

    Thank you!