Customizing Navigator with parent entry

It seems, that puting the parent navigator entry in any other custom client file is working.
 

Seems that customizing the SrvconNavigator.client is somehow treated specially...

@Nils Wendelöv Any Idea on above ? 

Without any deeper investigation done, it do look like a limitation/defect.

 I had the same issue and noticed that this is for all customized files. The navigator entries added onto customized files cannot be interdependent. For example, I added a navigator entry on one cust client and tried to use it as the parent in another cust client, but it says the parent navigator entry is not found.

As a workaround, there were a few options which worked for me:

1. If possible move the parent and child navigator entries to one client file
   (Another issue that I noticed was that in a core file that is customized, for example Shipment-Cust, even if the entries are both in the same file we get the same error saying the parent navigator entry is not found. This issue is not there in newly created files in the Cust layer)
    
2. The other option if there are too many child dependencies, an internal link can be used instead of moving the client elements into one client file.

​@hamalk 

​@Rakuse 
Any news on that topic? Did R&D have a look into this matter?

Client FW team should provide their insights

Ping ​@Nils Wendelöv , ​@Pavani De Silva ​@Rakuse 

No, we haven’t. As far as I’m aware, no defect has been logged with a reproducible test case, which is why I doubt it would have been addressed.

Hi ​@Pavani De Silva  Van you pls direct this to the relevant team pls ? 

​@flestephs ​@hamalk this is defined in the docs. It can be done in a client or a fragment. Use the toplevel entry

https://docs.ifs.com/techdocs/26r1/060_development/022_user_interface/030_aurena_dev/100_how_to_develop_aurena_pages/020_create_a_simple_aurena_page/?h=toplevel