2023 – January – NOTICE

Data Braider is being updated and relaunched shortly with new features and a reduced price.

This page is present as it will be updated at the same time.

Have you ever tried to connect to Microsoft Dynamics 365 Business Central’s API and found you just needed one more field? Or a table that wasn’t available?

You had to write a spec and ask a dev, or build the API page/query yourself to solve the problem, right?

Wouldn’t it be better if you could just adjust your API?

With the SBI Data Braider solution, you can work with your API data the same way you’re used to from Configuration Packages.

Easy to use and adjust.

Not only can you choose the table and fields you want to present, but you can also attach related information.

Great for getting into Flow, and powerful for coordinating with Integration Partners.

Additionally, you can apply filtering to data, making sure that your end-point only presents the information you want.

Adding a field to your API really does become as simple as “Check another box”.

Right within Business Central, you can generate a preview dataset to easily send formatting samples to your integration partners or even just to check the data yourself.

The data is presented in an easy-to-consume format (JSON).

Easy to read and understand!

Each record includes Primary Key info for easy troubleshooting. Additionally, it also presents all the SystemId values of the records, so you can easily hook multiple API endpoints together, as is often needed in Power Automate.

Including the names of all Tables and Fields ensures it’s easy to map the data in spreadsheets, Power BI, and more.

Understanding the API data should not be a mystery!

Can I also write to these API endpoints?

Not at this time. We do have a similar solution planned for 2022 on the write-back side, but we didn’t want to hold back on releasing this beautiful solution any longer than absolutely necessary.

What will this cost?

The cost is €140 per month per Business Central installation/production environment. Most people will spend well over 1-2 days of development and consulting hours per year, so the ROI on this is potentially substantial and also immediate.

Are there any limitations?

As mentioned, this is read-only, so it’s not a full “API”. We have tested this and things seem to run well with up to 5k-10k records, depending on complexity. So, if you’re working with large datasets, you will find that the performance is better with a Query API.

For help in learning how to authenticate or develop full Page or Query API end-points, please check with Arend-Jan Kauffman’s course offerings.

When can I have it?!

Right Now!

It’s available on AppSource here.

You’ll need to Activate it with a License Key for your subscription, which you can purchase here.

If you are running On-Prem or private cloud, please reach out to us for BC License updates and a runtime app version.