Creating metadata / Custom BO Objects throught OData services PMS

[vangelis_sanchoyerto]

Dear all,

We have the necessity to integrate a custom app with ByDesign or SAP Business One as the backend. The problem is at the point of creating our custom metadata (Business Objects in ByDesign and UDOs/User tables in SBO) directly from the app as an initialization process through each system APIs.

SAP Business one allows to create this metadata through the Service Layer.

In ByDesign unfortunately we haven found similar APIs in the Public Solution Model (PMS) or OData services available through the Odata Model Editor...

Any ideas?

Thanks Beforehand,

Vangelis

Postdata:

We already know that you could create the Custom BO (Business Objects) manually throught a Solution that you would later implement at each client repository but the idea is to automatize this part in the app.

We saw the part about "Exceptional Cases for Scalable Solutions" in the SDK Documentation but in that keys it states "If SAP agrees to your request, you will receive instructions on how to proceed in the studio." not any mention about the API way of doing it...

[thiago]

Hello Vangelis,

Creating the metadata is not possible in ByD through its APIs as of today.
The "Scalable Solutions" mentioned in the SDK documentation refers to the Multi-Customer Solution. Check this document.

The alternative for your scenario would be to keep the custom metadata and data in a persistence layer at your application level instead of using the core ERP resources. How do you see that?

Regards,
Thiago.

[vangelis_sanchoyerto]

Thanks for the anwser,

We checked the feasibility of that and keeping that data of the clients in the persistence layer instead of using each client backend generates the following problems:

• You have to somehow handle correctly the procedures for keeping customer data in your environment and the legal requirements associated (GDPR in Europe, and local regulations in each country...LOPD in Spain for example).
• You have to take into account the exponential costs of processing power,storage, TOC, technical maintenance, etc... for hosting all that data that will increase along with number of clients / quantity of data each client has.
• Yo have to devise a good tenant system (Multitenancy) to host that data and prevent mixing it between clients and not reaching the selected database vendor / technology limits.

One possibility would be using an adaptation layer that internally would use the client backend for SAP Business One clients (through Service Layer) and the persistence layer for de ByD clients, but certainly is a big problem that adds more complexity to the solutions so we must think about it.

Its sad that being both SAP Business One and ByD products of SAP it seems that ByD is treated as a second class citizen...

Best regards,

Vangelis

[thiago]

Hello Vangelis,

Thanks for the assessment.
All the three bullets you mention are of central importance and/or best practice for any legal compliant and scalable software.
So you would have to take them in consideration even if we had the API for handling metadata in ByD at this very moment.
At SAP we are continuously taking partners' and customers' feedback to improve our products and deliver best in class software.
This is being discussed internally, but you can also log a request in the influence portal.

Regards,
Thiago.