How to create extension project from standard CRM Fiori application

Pre-Steps: You should know how to run CRM Fiori 1.0 applications in WebIDE first.

Next, we will create a extension project out the My Opportunities app we cloned in our WebIDE workspace, what’s the advantage over create the extension project out of a remote resource? Well, you’ll have both the standard application and the extension application in the same workspace, and also, you can play around with the standard application, change a thing or two for experiment, and your extended app will pick up the changes made in the standard application right away, sounds good?

Step 8. There’s actually a neo-app.json existed already when we first cloned the app, but it does not really works, that’s why we created our own. In order to create a extension project out it, we can’t have two neo-app.json file, that’s why in this step, what we will need to do is to rename this file to something the system won’t be able to recognize.

Step 11. Again, we’ll need to update the neo-app.json file of the extended app, so that you can connect it to your gateway system (you need to update gateway connection part in json file), and also, to eliminate the library.js not found error you may encounter.

Once that’s done, you’re good to go, happy coding

{
"routes": [
{
"path": "/sap/opu/odata",
"wattUsage": "odata_abap",
"target": {
"type": "destination",
"name": "your_gateway_name",
"entryPath": "/sap/opu/odata"
},
"description": "your_gateway_description"
},
{
"path": "/src/main/webapp/resources/",
"target": {
"type": "service",
"name": "sapui5",
"entryPath": "/resources"
},
"description": "SAPUI5 Resources"
},
{
"path": "/src/main/webapp/resources",
"target": {
"type": "application",
"name": "cuscrmlibreuse",
"preferLocal": true
},
"description": "Reuse Library"
}
]
}