on 04-01-2015 12:04 PM
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
it could be because of the same model name used in the extended project
Change the name to ZHCM_TEAM_CALENDAR_SRV, and see if it helps..
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 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.