# Why do some \`system\` functions take keyword args and some don't?

**URL:** <https://forum.inductiveautomation.com/t/why-do-some-system-functions-take-keyword-args-and-some-dont/76764>\
**Category:** Ignition\
**Created:** [July 24, 2023, 5:20am UTC](https://forum.inductiveautomation.com/t/why-do-some-system-functions-take-keyword-args-and-some-dont/76764 "2023-07-24T05:20:47Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 24, 2023, 3:53pm UTC](https://forum.inductiveautomation.com/t/why-do-some-system-functions-take-keyword-args-and-some-dont/76764/6 "2023-07-24T15:53:09Z")

</div>

I only use them when there's a mix of required and optional parameters, and even then sparingly.

They're a bit of a footgun in some cases, and can lead to mistakes and confusion like [this](https://forum.inductiveautomation.com/t/rest-api-system-net-httpclient-post-errors-415-400/76744/2) if you don't name every parameter in your calls and instead fall back to the implicit ordering.

---

_[View the full topic](https://forum.inductiveautomation.com/t/why-do-some-system-functions-take-keyword-args-and-some-dont/76764)._