Relationships bug

Posted by matman on 08-Sep-2014 02:57

In the past I created a relationship between an Employer and Employee object. Even though I deleted the Employee record, it still seems to be stored in the list of related Employees. Picture 1:

Picture 2:

As you can see, there are only 3 Employee records, yet 5 are shown when requesting all related Employee records to the Employer. I smell a bug, do you smell a bug? (Note: I remember that 108195717 is a record of an Employee I deleted a while ago.)

All Replies

Posted by matman on 08-Sep-2014 03:33

Unsurprisingly, it cannot find the related record values when iterating through them:

Posted by Manooj Murali on 08-Sep-2014 03:36

Checking with the dev team here if this issues is anyway related to Will post back.

Posted by Santosh Patel on 08-Sep-2014 03:39

Hi Matman,

A workaround until things are confirmed would be keep your recyclebin clean (if not completely at least the records of type employee)


Posted by Manooj Murali on 08-Sep-2014 03:42

If what [mention:7e24e60fbecc4ff8baf4669a65bae0a0:e9ed411860ed4f2ba0265705b8793d05]  suggested, fixes your issue then may be this indeed is related to the case we are already looking into. So, please let us know the suggested work around works for you.

Posted by matman on 08-Sep-2014 04:04

Unfortunately I cannot open your link because I don't have access to the support platform (I'm using trial). After cleaning the recycle bin, the "Original Formula" section no longer shows the ID's that don't exist. However, when u take a look at the "Parsed Formula" section, u'll notice that the LOOP output is the same as the previous picture (3 empty iterations):

Posted by Santosh Patel on 08-Sep-2014 04:13

Of course these would be addressed by the bug around the issue. From your result I see that it only shows the two employees. It would do good to have some sanity checks on the loop variable (empty/undefined check on .name or other fields used) and proceed with processing only if you find valid values  until the bug is fixed.


Posted by matman on 08-Sep-2014 05:15

I'm happy to report that sanity checks seem to be unnecessary. rbv_api.getFieldValue() returns correct database values:

The bug won't cause me any problems, I was actually busy setting a trigger on 'after update' to permanently delete records that were removed from the relationships list of the Employer.

Thanks a lot for the support! Is there any way I could get access to the support platform? I'm doing research for a company to see if we could start using Rollbase for our purposes.

Posted by Santosh Patel on 08-Sep-2014 05:41

Support Account is available only for paid customers. You could signup for a one user developer account. That will entitle you for a support account.

Having said that this forum will gladly help you out with any questions you might have.


Posted by Godfrey Sorita on 11-Sep-2014 15:22
I noticed a slight difference on the related case. Defect PSC00313672 has been filed for this defect, instead. Will keep you posted for any updates.
Posted by matman on 12-Sep-2014 04:47


Posted by matman on 19-Nov-2014 08:44

Have there been any updates regarding this defect? Because of recently discovered Rollbase limitations I had to add triggers, but they won't run when my fields refer to records in the recycle bin.

Posted by Godfrey Sorita on 19-Nov-2014 09:25
The fix is included in Rollbase release which is scheduled for December 2014.
Posted by matman on 19-Nov-2014 09:26

Great! Thanks a lot!

This thread is closed