Unable to use Annotation Modeler with oData Service containing slashes

[Former Member]

I created a project in SEGW entirely with the following namespace: /abc/, now I'm facing some problems due to "/" (slashes) in the oData Service.

I'm trying to build an application based on a list report template (using SAP Web IDE) and when I try to make use of the Annotation Modeler, it shows me an error msg:

"Unhandled Error: Cannot read property 'addChild' of undefined".

After a few tests and some googling, I found out that the problem is within these "/" on my namespace.

I know that there is a recommendation where I can't use "/" on oData Service name, but I have to use that namespace. What can I do to solve my problem? Is there a way to solve it?

Prerequisites to work with Annotation Modeler:

https://help.hana.ondemand.com/webide/frameset.htm?a06faccfc98443d89b07011e1b9cf485.html

[Former Member · Accepted solution]

Hi Andrew,

You have to remove "/" of the schema namespace for the Data Model in the project. For example: /abc/project => abc_project.

The link below explains how to do that. Let me know if it works for you.

https://help.sap.com/viewer/68bf513362174d54b58cddec28794093/7.51.1/en-US/491b39cbcac849dd8727c60f64...

[Former Member · Accepted solution]

Thanks! It worked.

[goncalvesp · Accepted solution]

In case the help page get's buried:

1. Open the gateway project.
2. Right click Data Model folder.
3. Select Details.
4. In the field "Schema Namespace" enter a schema namespace for this project. If this field is left blank, Schema Namespace is generated and populated after runtime generation based on Technical Name of the project

Note: Special characters (apart from '.' and '_') are not allowed.

A colleague was trying to use a service created under a namespace with slashes (/XXX/<SERVICE_NAME>) and the solution was to basically change the schema namespace into XXX(dot)<SERVICE_NAME>.

[smith_john]

its a bug ... we had the same issue, there's a note to fix it, search OSS.

[former_member412549]

Hi smith.john,

Can you point me towards, the OSS note you have mentioned in above comment or it'll be very helpful if you share the Note no.

Thanks & Regards,

Tushar Sharma

[maryana_naboka]

Hi Tushar,

I guess Neil means this note: https://launchpad.support.sap.com/#/notes/2444661 which is targeted for fixing such issues at Gateway.

To overcome such issue for for customer namespace, you should modify the schema namespace for the Data Model in the project as explained in the documentation: https://help.sap.com/viewer/68bf513362174d54b58cddec28794093/7.51.1/en-US/491b39cbcac849dd8727c60f64...

Hoep this helps,

Mariana