Skip to Content

How to create Things via oData - samples available?

Hi experts,

I have been able to create a Thing on IoT AE and link it to my device on IoT Services by using the IoT AE Thing Modeler cockpit.

I have seen there are REST and oData APIs, and the oData APIs are the way to go.

Is the IoT AE cockpit using oData or REST APIs to create the Things?

If I want to use the new oData APIs, are there any tutorials/samples showing how to proceed?
I'll like to take advantage of the Flexible Mapping explained in the help: https://help.sap.com/viewer/350cb3262cb8496b9f5e9e8b039b52db/1.73.0.0/en-US/2a1e7b5202924322a474f494aa2156ab.html but I don't know from where to start with.

Thanks,
Trinidad.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Mar 25 at 10:55 AM

    Hi,

    the thing modeler apps (packages, thing types, property catalog) come in 2 flavors. It depends on the roles assigned to the role collection assigned to your user which one is showing up in the fiori launchpad. Since January we recommend to for new models start using the odata variant based on the Thing_Endingeer_Odata role template and the corresponding apis. If you had built your thing model based on rest-apis or apps then I suggest you trigger the migration of the meta-data (which will keep your things and your sensor data intact) by opening a ticket with IOT-BSV-TS. After this migration you can use the odata variant of apis and apps.

    We are updating the tutorials for odata right now - but in the thing modeler the difference is small. Instead of defining the mapping at the thing level you do it first at the thing type/sensor type level under the new "connectivity" tab and then you assign the thing to a sensor at the thing level in the tab of the same name.

    Regards, Marcus

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Marcus,

      Thank you for your answer it has helped me to solve the issue!

      I had both roles "iotas_Thing_Engineer_Fiori_Launchpad" and the "iotas_Thing_Engineer_Odata" assigned, just had to go to the IoT tenant and select the Thing Modeler and other oData tiles to be visible (this migration document helped me to better understand).

      Now I have then access to both the REST and oData apps.

      I have been able to create a new package and ThingType and connect it to my IoT Device! The oData apps are more flexible, thank you for proposing me to use them!

      Thank you,
      Trinidad.