That N+1 problem refers to a query pattern where an application starts a separate, separate query for each additional detail instead of retrieving the data in a consolidated manner. This pattern leads to many individual queries and unnecessary network overhead.
Example of webhooks
Webhooks from SAP Business One have so far only provided the key to an object in the basic format, such as the DocEntry of an invoice. For each additional detail, the recipient therefore had to make a separate query to the service layer. The N+1 problem was thus a central technical problem of previous webhooks.
Solution with Feature Package 2608
With Feature Package 2608, the Service Layer sends selected fields directly with the event via BizObjProps. This provides the recipient with more context, rather than just the key. This enrichment of the usage data reduces the number of subsequent requests.
Avoidance when querying the service layer
This pattern can also be avoided by asking the service layer directly. The application first collects the required keys. Then it aggregates the data sets using an OR filter. Additionally, it only queries the required fields using $select.
Shopware 6 for SAP Business One
SAP Business One and DATEV - Synchronised
DATEV and SAP Business One Export & Import
Electronic invoices to authorities
SAP Business One Connect for carriers
