Skip to Content

Fiori Launchpad - odata error 404 extension launchpad

I'm creating an extension to launchpad. I want to put a dynamic message on the launchpad screen.
So I need to bind data.

In an application of the current launchpad, I reach to get metadata with a get request.

In the extension, I've got error 404.

When I try the address in the gateway service test, I have status 200

But when I run in webide, I have an error 404. And I don't reach to bind data.

Could you help me ?


Here is the code :

            var sUrl = "/sap/opu/odata/sap/ZWOC_ECOMMERCE_SRV/";
            var oDataModel = new sap.ui.model.odata.v2.ODataModel(sUrl, {
                json: true,
                loadMetadataAsync: true

  "/UserLPSet('USER')", {
                success: function (oData, response) {
                        var oJSONModel = new sap.ui.model.json.JSONModel();
                    } //function

            var oRenderer = sap.ushell.Container.getRenderer("fiori2");
            oRenderer.addSubHeader("sap.m.Text", {
                id: "testBar"
            }, true, true);
            var oBar = sap.ui.getCore().byId("testBar");
status200.jpg (44.4 kB)
status200.jpg (84.6 kB)
404.jpg (68.2 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Jan 27, 2019 at 05:23 AM

    Is the launchpad running on SAP Cloud Platform (portal service) or is it running on a Netweaver box (e.g. SAP NW Gateway)? From the looks of your Gateway Client screenshot I'm going to assume that the OData service and the Fiori Launchpad (FLP) are running on the same box.

    I noticed three things right away. They might not be the cause, but they will get us started

    1) You are testing using a local run on Web IDE. How does Web IDE (and Cloud Platform) know what /sap/opu/odata/sap means? Do you have a neo-app.json file which maps that path to a Cloud Platform destination? Do you have that for the launchpad plugin? What happens if you deploy your plugin app to the gateway box and run it there?

    2) I don't believe you should instantiate the OData service and then call it right away. You should wait for the metadataloaded event

    3) Have you tried it without the loadMetadataAsync property? If you address #2 then this might no longer be an issue

    Given that the issue you have is with the metadata loading in the first place I don't think addressing #2 or #3 will help. It's more important to look at #1.

    If you could share your GIT repo (make it public) that would be a help

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.