Discussions

We extended a lot of default iMIS objects to fit our needs. In a lot of cases we build custom stored procedures to populate these tables and work around iMIS iparts. Our stored procedures typically consist out of two inserts; 1 is the imis default table and 2 is our custom table.
This design is dated and if we want to go to the cloud we have to change this approach.

The Rest API should be the way to go but im wondering if its possible to do one rest call to populate a default imis table and our custom table or would this also mean two separate calls?
It would be nice if we can wrap our custom object and the imis object into one object that handles identity inserts when doing POST/PUT/GET/DELETE.

What would be the way to go?