Handling Long Field Names in OData / RAP API’s

Estimated read time 1 min read

Requuirement:-

While working with OData services in SAP, you might encounter an issue when sending long field
names like: PuchaseOrdernosendtosalesforcesystem

In such cases, your CDS view might throw an error due to the length or naming restriction.

Error Description

 

Solution

Use the annotation below to define the desired long field name explicitly:

@odata.property.name: ‘PuchaseOrdernosendtosalesforcesystem’

After adding this annotation, activate your CDS view, and then create:

Service DefinitionService Binding (V4)

Output on POSTMAN / SAP Gateway

This simple technique helps you maintain meaningful field names without breaking technical limits in Odata API’s.

Thanks

Dinesh Kumar

 

​ Requuirement:-While working with OData services in SAP, you might encounter an issue when sending long fieldnames like: PuchaseOrdernosendtosalesforcesystemIn such cases, your CDS view might throw an error due to the length or naming restriction.Error Description SolutionUse the annotation below to define the desired long field name explicitly:@odata.property.name: ‘PuchaseOrdernosendtosalesforcesystem’After adding this annotation, activate your CDS view, and then create:Service DefinitionService Binding (V4)Output on POSTMAN / SAP GatewayThis simple technique helps you maintain meaningful field names without breaking technical limits in Odata API’s.ThanksDinesh Kumar   Read More Technology Blog Posts by Members articles 

#SAP

#SAPTechnologyblog

You May Also Like

More From Author