cancel
Showing results for 
Search instead for 
Did you mean: 

Getting Detail page on first time application load instead of master

Former Member
0 Kudos

Hi Experts,

I have a custom fiori app, build on 1.28 with XML views and routing. My master page has 7 input fields in Vbox and a search button. Detail view has empty message page. When i open app in desktop view, i can see correct master and detail loaded. But when i open application in mobile view (chrome emulator), I see detail (Empty) page loaded first. Where as I am expecting Master page with input fields to be displayed. Is this by design? Or am i doing something wrong.

Please suggest.


Thanks

Pranav

Accepted Solutions (1)

Accepted Solutions (1)

Chantele
Active Participant
0 Kudos

Hi

please can you post the code with your routing?

In you app.view.xml file have you set the split app mode to stretchcompressmode as below


<SplitApp id="fioriContent" showHeader="false" mode="StretchCompressMode">

Chantele

Former Member
0 Kudos

Thanks Chantele.

With StretchCompressMode, both master and detail page is visible for iphone6 screen size. Working fine with smaller screens like iPhone4/5.

Here is what i have in manifest.json

"routing": {

  "config": {

  "id": "appRouter",

  "routerClass": "sap.m.routing.Router",

  "viewType": "XML",

  "viewPath": "com.view",

  "controlId": "app",

  "transition": "slide",

  "bypassed": {

  "target": ["home", "toEmpty"]

  }

  },

  "routes": [{

  "pattern": "",

  "name": "appHome",

  "target": ["home","toEmpty"]

  },

  {

  "pattern": "Empty",

  "name": "Empty",

  "target": "toEmpty"

  },

  {

  "pattern": "MaterialDetail",

  "name": "MaterialDetail",

  "target": ["home","toMaterialDetail"]

  },

  {

  "pattern": "ReservationItemList",

  "name": "ReservationItemList",

  "target": ["home","toReservationItem"]

  }],

  "targets": {

  "home": {

  "viewName": "GoodsIssueSearch",

  "viewLevel": 1,

  "controlAggregation": "masterPages"

  },

  "toEmpty": {

  "viewName": "Empty",

  "viewLevel": 2,

  "controlAggregation": "detailPages"

  },

  "toMaterialDetail": {

  "viewName": "MaterialDetail",

  "viewLevel": 3,

  "controlAggregation": "detailPages"

  },

  "toReservationItem": {

  "viewName": "ReservationItemList",

  "viewLevel": 2,

  "controlAggregation":"detailPages"

  }

  }

Thanks

Pranav

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Experts,

I am still not able to find out root cause. Any help is highly appreciated.

Thanks

Pranav