4

Solved: Building side-by-side extensions on SAP BTP - Manu... - SAP Community

 6 months ago
source link: https://community.sap.com/t5/sap-learning-q-a/building-side-by-side-extensions-on-sap-btp-manual-deployed-fiori-app-not/qaq-p/13616191
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Building side-by-side extensions on SAP BTP - Manual Deployed Fiori app not working

dvvelzen

Participant

3 weeks ago

- last edited

2 weeks ago

During the learning I've deployed the risk-management app to my trial.

https://learning.sap.com/learning-journeys/build-side-by-side-extensions-on-sap-btp/exercise-perform... 

However when I try to "Go" get the data I get this error.

dvvelzen_0-1708622443664.png

The srv part crashes, it relates to this part of the code:

dvvelzen_1-1708622542150.png

Running it locally in BAS works fine.

I noticed the difference between the BTP trial deployment and the BAS local run is in the req.query.SELECT.columns that is constructed. The deployed Cloud (HANA) version has a link to the virtual columns and a limit, where the BAS run against sqlite doesn't have this:

{
  "BTP_req.query.SELECT": {
    "from": {
      "ref": [
        "RiskService.Risks"
      ]
    },
    "orderBy": [
      {
        "ref": [
          "ID"
        ],
        "sort": "asc"
      }
    ],
    "columns": [
      {
        "ref": [
          "ID"
        ]
      },
      {
        "as": "PrioCriticality",
        "cast": {
          "type": "cds.Integer"
        },
        "val": null
      },
      {
        "as": "criticality",
        "cast": {
          "type": "cds.Integer"
        },
        "val": null
      },
      {
        "ref": [
          "impact"
        ]
      },
      {
        "ref": [
          "owner"
        ]
      },
      {
        "ref": [
          "prio_code"
        ]
      },
      {
        "ref": [
          "title"
        ]
      },
      {
        "ref": [
          "prio"
        ],
        "expand": [
          {
            "ref": [
              "code"
            ]
          },
          {
            "ref": [
              "descr"
            ]
          }
        ]
      },
      {
        "ref": [
          "miti"
        ],
        "expand": [
          {
            "ref": [
              "ID"
            ]
          },
          {
            "ref": [
              "descr"
            ]
          }
        ]
      }
    ],
    "limit": {
      "rows": {
        "val": 30
      },
      "offset": {
        "val": 0
      }
    }
  },
  "BAS_req.query.SELECT": {
    "from": {
      "ref": [
        "RiskService.Risks"
      ]
    },
    "orderBy": [
      {
        "ref": [
          "ID"
        ],
        "sort": "asc"
      }
    ],
    "columns": [
      {
        "ref": [
          "ID"
        ]
      },
      {
        "ref": [
          "PrioCriticality"
        ]
      },
      {
        "ref": [
          "criticality"
        ]
      },
      {
        "ref": [
          "impact"
        ]
      },
      {
        "ref": [
          "owner"
        ]
      },
      {
        "ref": [
          "prio_code"
        ]
      },
      {
        "ref": [
          "title"
        ]
      },
      {
        "ref": [
          "prio"
        ],
        "expand": [
          {
            "ref": [
              "code"
            ]
          },
          {
            "ref": [
              "descr"
            ]
          }
        ]
      },
      {
        "ref": [
          "miti"
        ],
        "expand": [
          {
            "ref": [
              "ID"
            ]
          },
          {
            "ref": [
              "descr"
            ]
          }
        ]
      }
    ]
  }
}

Can anyone explain why this difference is there?


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK