Aurena NavigationLink

Hello, @LakmaliRD .  That is good to know, thank you!  Do you know what the severity level is and if we can get a patch?  We have just gone to Update 9 and have ordered Update 11, so we’re not going to install Update 10. 

Thank you,

Joann

Hi @jtobin ,

If you are unable to wait till UPD11, please send a request to RnD via a support case.

@LakmaliRD  Thank you!

@LakmaliRD Thank you for the information. Is there a workaround until we get UPD10 for this

@LakmaliRD Ifsapp version is Aurena UPD11 But still I’m getting database value when I try to navigate from a custom window. Since the field is a reference field this is causing problems. 

Am I doing anything wrong or are the issues still exist for custom LUs

Hi,

Even we have the same issue in UPD 11 and data is not filtering as per the navigation filter conditions.

Hi all,

We managed a work around for this issue (on UPD9), where we simply overwrite the NavigateFilter, to read again the Aurena Field name (thus as per above screenshot, we overwrite it back to “CustomerId”)