API request incompatible with Orion-LD

[markendos]

I'm trying to create a productOrder using the productOrderingManagement API with Orion-LD as my CB but POST request sent to Orion fails.

• This is my request:

curl --location 'http://<tm_forum_api_host>/tmf-api/productOrderingManagement/v4/productOrder' \
--header 'Accept: */*' \
--header 'Content-Type: application/json' \
--data '{
    "productOrderItem": [
        {
            "id": "random-order-id",
            "action": "add",
            "productOffering": {
                "id": "urn:ngsi-ld:product-offering:<existing_product_offering_id>"
            }
        }
    ],
    "relatedParty": [
        {
            "id": "urn:ngsi-ld:organization:<existing_organization_id>"
        }
    ]
}'

• Request sent from the TM Forum API service to the CB:

curl --location 'http://<orion-ld_host>/ngsi-ld/v1/entities' \
--header 'Content-Type: application/json' \
--data '{
    "href": {
        "value": "urn:ngsi-ld:product-order:<product_order_id>",
        "type": "Property"
    },
    "productOrderItem": [
        {
            "value": {
                "itemId": "random-order-id",
                "action": "add",
                "productOffering": {
                    "id": "urn:ngsi-ld:product-offering:<existing_product_offering_id>",
                    "referencedTypes": [
                        "product-offering"
                    ],
                    "entityId": "urn:ngsi-ld:product-offering:<existing_organization_id>"
                }
            },
            "type": "Property",
            "itemId": {
                "value": "random-order-id",
                "type": "Property"
            },
            "productOffering": {
                "object": "urn:ngsi-ld:product-offering:<existing_product_offering_id>",
                "type": "Relationship",
                "referencedTypes": {
                    "value": [
                        "product-offering"
                    ],
                    "type": "Property"
                },
                "entityId": {
                    "value": "urn:ngsi-ld:product-offering:<existing_product_offering_id>",
                    "type": "Property"
                }
            },
            "action": {
                "value": "add",
                "type": "Property"
            }
        }
    ],
    "relatedParty": [
        {
            "object": "urn:ngsi-ld:organization:<existing_organization_id>",
            "type": "Relationship"
        }
    ],
    "orderDate": {
        "value": "2025-05-08T11:10:09.304600775Z",
        "type": "Property"
    }
}'

• Logs in the Orion-LD service:

DEBUG@11:10:09  orionldContextItemExpand.cpp[85]: Found 'entityId' in the core context (https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.8.jsonld) 
ERROR@11:10:09  pCheckAttribute.cpp[217]: ***** ERROR: JSON Type for attribute not according to @context @type field: https://uri.etsi.org/ngsi-ld/entityId (status: 400) 
DEBUG@11:10:09  mhdReply.cpp[77]: Response Body: '{"type":"[https://uri.etsi.org/ngsi-ld/errors/BadRequestData","title":"JSON](https://uri.etsi.org/ngsi-ld/errors/BadRequestData%22,%22title%22:%22JSON) Type for attribute not according to @context @type field","detail":"[https://uri.etsi.org/ngsi-ld/entityId"}'](https://uri.etsi.org/ngsi-ld/entityId%22%7D%27) 
DEBUG@11:10:09  mhdReply.cpp[78]: Response Code:  400

Versions used:

• FIWARE TM Forum API v1.2.7
• Orion-LD v1.9.0

I have also tested with latest version of Scorpio CB and older versions of Orion-LD with the following results:

• Scorpio: works in all tested versions including v5.0.9 (latest stable)
• Orion-LD: works in tested versions up to v1.0.1

[wistefan]

Hi, thanks for the report. The automated tests run with Orion-LD v1.8.0. Can you confirm that its also not working with that version?
Could you please provide a test to reproduce the issue?

[markendos]

Hi, thanks for the report. The automated tests run with Orion-LD v1.8.0. Can you confirm that its also not working with that version? Could you please provide a test to reproduce the issue?

Hi @wistefan I can confirm that the issue is present for version v1.8.0 as well. I have been able to trace the problem back to this PR. The issue is basically with the automated attribute mapping from the ReferenceValue entity extended by ProductOfferingRefValue which is not treating the getEntityId as a getter for the id attribute, but instead is mapping an "unexpected" entityId into the object sent to Orion. Since entityId is an attribute defined in Orion-LD's core context, the request fails as detailed in the issue.

A simple patch can be applied by adding the @JsonGetter("id") annotation to the getEntityId method (and a @JsonIgnore to the getReferencedTypes would be nice as well).

As far as testing, further changes would be necessary to generate the ProductOfferingRefValueVO class and subsequent test classes, as well as a way to allow creation of ProductOffering entities in the product-ordering-management test context.

[wistefan]

Hi, thanks for clarifying. Will you provide a PR with the fixes?

[markendos]

Hi, any updates on this issue?

[wistefan]

Hi @markendos ,
I did not yet look deeper into that yet, but just found another issue with Orion-LD. Its lack of support for datasetId in queries makes it incompatible for retrieval of multiple objects in TMForum. Thus, I would recommend to not use Orion-LD as broker for TMForum until it fully supports datasetId.