cancel
Showing results for 
Search instead for 
Did you mean: 

Deploying Standard and Extended app together

kammaje_cis
Active Contributor
0 Kudos

Hello Experts,

For demo purpose I am deploying standard and extended "My Team Calendar" apps together (in a same catalog for users).

I am encountering a strange behaviour.

My extended app's only extension is replacing the standard OData service by a custom oData service.

This is how I did it. (generated by WebIDE)


this.hcm.myteamcalendar.Component.extend("ZHCM_TEAM_CALExtension.Component", {

  metadata: {

  version: "1.0",

  config: {

  "sap.ca.serviceConfigs": [

  {

  name: "HCM_TEAM_CALENDAR_SRV",

  serviceUrl: "/sap/opu/odata/sap/ZFIORI_TEAM_CALENDAR_SRV/",

  isDefault: true,

  mockedDataSource: "./model/metadata.xml"

        }

    ]

  },

  customizing: {}

  }

});

Problem:

When I load the Fiori Launchpad and click on Standard "MyTeam Calendar" app, it uses the standard OData service. No problems.

When I click on Extended "MyTeam Calendar" app, it uses the custom OData service. No problems.


Now, if I click on Standard app again, it starts using the custom OData service. Am I doing anything wrong here?


Thanks

Krishna

Accepted Solutions (0)

Answers (1)

Answers (1)

SandipAgarwalla
Active Contributor
0 Kudos

it could be because of the same model name used in the extended project

  1. config: { 
  2.   "sap.ca.serviceConfigs": [ 
  3.   { 
  4.   name: "HCM_TEAM_CALENDAR_SRV"

Change the name to ZHCM_TEAM_CALENDAR_SRV, and see if it helps..

kammaje_cis
Active Contributor
0 Kudos

But that is how Fiori infra redirects the standard app to use custom service. If I change the name parameter, then my Z service is never called.