Issue with two Main Lookup / Link Lookups in the same object

Posted by Meryk on 14-Aug-2015 06:48

Hi,

I have 3 lookup fields A, B, and C, on the view page of an object myObject.

myObject - A is a Main lookup, and B-A is a Link lookup.

Same, myObject-B is a main lookup and C-B is a Link lookup.

So we have 2 levels of Main lookup/Link lookup.

This lookup fields are actually pick lists. 

The issue I am facing, is that when I select a value in each one of the 3 above pick lists and save, the values are saved normally. When I click Edit and open the Edit Page, the pick list C is empty.

When I removed the second Main lookup/Link lookup, it was not emptying the 3rd pick list, so it looks like a bug when having 2 levels of Main lookup/Link Lookup.

Are you aware of that or can you give us some guidelines on this please ?

Thank you 

Mery

Posted by Anoop Premachandran on 04-Sep-2015 02:03

Please log support case with App XML

All Replies

Posted by spope-rollbase on 16-Aug-2015 15:56

Mery,

We have been complaining about this issue for months, and getting little traction.

We managed to figure out a workaround involving adding a script component to your affected edit pages:

refer: community.progress.com/.../18579.aspx

for details of the suggested workaround.

Good luck

Steve Pope (Linx)

Posted by Mohammed Siraj on 27-Aug-2015 05:49

Unable to reproduce the issue with the above stated set of instructions.

Request you to share a sample app xml with Object configurations as defined above.

Regards,

Siraj.

Posted by Anoop Premachandran on 04-Sep-2015 02:03

Please log support case with App XML

Posted by Mohammed Siraj on 10-Sep-2015 22:49

This is is valid issue. It  is specifiic to link lookup fields which are configured as picklist. It is a timing issue, wherein, we need to sync between threads that fetch field values with respect to their main look up field.

We are tracking this as Issue:PSC00340520 & it will be addressed in forthcoming releases.

Posted by Meryk on 18-Nov-2015 05:48

Hi Siraj,

Please is this fixed in 4.0.3?

Thanks,

Meryem

Posted by Mohammed Siraj on 18-Nov-2015 06:26

Yes Meryem, this has been resolved in 4.0.2 release itself.

This thread is closed