Global Model Not Accesible

Avoid setting models on the Core directly if you’re using Components. Components are meant to be independent and reusable parts and therefore will not inherit the Core models by default. Models should be set depending on your business case:

• Models declared in the app descriptor (manifest.json) section /sap.ui5/models will be set on the Component. They are automatically propagated to its descendants. Given default model, the following returns true:

  this.getOwnerComponent().getModel() === this.getView().getModel() // returns: true
  

  Note: calling this.getView().getModel() in onInit will still return undefined since the view doesn’t know its parent at that moment yet (this.getView().getParent() returns null). Therefore, in onInit, call the getModel explicitly from the parent that owns the model. E.g.:

  { // My.controller.js
    onInit: function {
      // The view is instantiated but no parent is assigned yet.
      // Models from the parent aren't accessible here.
      // Accessing the model explicitly from the Component works:
      const myGlobalModel = this.getOwnerComponent().getModel(/*modelName*/);
    },
  }
  

• Set models only on certain controls (e.g. View, Panel, etc.) if the data are not needed elsewhere.

• Set models on the Core only if the app is not Component-based.

If Core models or any other model from upper hierarchy should still be propagated to the Component and its children, enable propagateModel when instantiating the ComponentContainer.

new ComponentContainer({ // required from "sap/ui/core/ComponentContainer"
  //...,
  propagateModel: true // Allow propagating parent binding and model information (e.g. from the Core) to the Component and it's children.
})

But again, this is not a good practice since Core models can be blindly overwritten by other apps on FLP as SAP recommends:

Do not use sap.ui.getCore() to register models.

---

About the Core model being undefined in onInit: This is not the case anymore as of version 1.34.0. The Core model can be accessed from anywhere in the controller. However, descendants of ComponentContainer are unaware of such models by default as explained above.