Bound Action vs Unbound Action

(0) Share

Report

Posted on by benovic

350

I an working on a API Endpoint and found that using an unbound action was a lot easier than a bound action. I wonder if bound actions are preferrable for light cases only?

What are the advantages of using bound actions?

What are the disadvantages of unbound actions?

All responses (3)

Answers (0)

YUN ZHU 78,675 Super User 2025 Season 1 on at

Like (0)

Report

RE: Bound Action vs Unbound Action

Hi, just adding some info.

Creating and Interacting with an OData V4 Bound Action

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-creating-and-interacting-with-odatav4-bound-action

Creating and Interacting with an OData V4 Unbound Action

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-creating-and-interacting-with-odatav4-unbound-action

Hope this helps as well.

Thanks.

ZHU
Inge M. Bruvik 999 Moderator on at

Like (2)

Report

RE: Bound Action vs Unbound Action

That all depends on your use case i think.

If you want to handle one specific record f.ex. post one single sales order - bound action is preferred.

If you just want to start a procedure that will handle multiple records and possible spanning several tables then you can use an unbound action.
DAnny3211 9,274 Moderator on at

Like (1)

Report

RE: Bound Action vs Unbound Action

hi

www.kauffmann.nl/.../

look this

DAniele