on 11-08-2023 9:53 AM
Hi,
I have a simple OdataV2 List report app built with the respective fiori elements template. In the manifest file I want to define a routing from an external URL to the initial index.html page. This takes place with the implementation of an extension controller. I have tried the below setting as a component routing but apparently it does not recognize the List report as a proper target. I got an error message "TemplateAssembler-dbg.js:320 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'registryEntry') at o.init (TemplateAssembler-dbg.js:320:51) " in the console screen. Do you have any idea how I can sort this out?
Thanks
"routing": {
"config": {},
"routes": [
{
"pattern": "toListPage",
"name": "toListPage",
"target": [
"ListReportExt"
]
}
],
"targets": {
"ListReportExt": {
"type": "Component",
"id": "ListReportExt",
"name": "sap.suite.ui.generic.template.ListReport"
}
}
}
I have figured the answer myself by debugging the standard scripts related to navigation. In the Fiori List Report template, the name of the initial target for the navigation is "root". Therefore applying below route leads to a correct navigation.
"route": [
{
"pattern": "toListPage",
"name": "toListPage",
"target": "root"
}
]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
8 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.