# Function signatures for syntax check

**URL:** <https://www.epiusers.help/t/function-signatures-for-syntax-check/103913>\
**Category:** Kinetic ERP\
**Tags:** function\
**Created:** [June 12, 2023, 3:01pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913 "2023-06-12T15:01:32Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Banderson](https://www.epiusers.help/user_avatar/www.epiusers.help/banderson/32/50875_2.png) [@Banderson](https://www.epiusers.help/u/Banderson)\
**Post date:** [June 12, 2023, 3:01pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/1 "2023-06-12T15:01:33Z")

</div>

Does anyone know how to fix this? If you mess with the signatures in the functions, the syntax checker can throw up false errors. Sometimes they will go away with recycling, but this one has been stuck even after moving the functions from environment to environment. It still saves and works fine, but there errors in the error list are super annoying.

 ![image](https://www.epiusers.help/uploads/default/original/3X/7/d/7d9474788de787138241475e1bb62b4d966f1cf6.png)

 ![image](https://www.epiusers.help/uploads/default/original/3X/d/0/d06f6a3eda2bbc3745d793ee68bedcad8dba6ae8.png)

---

<div class="post-metadata">

**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\
**Post date:** [June 12, 2023, 3:21pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/2 "2023-06-12T15:21:04Z")

</div>

I have noticed the same, but didn’t quite know how to describe it at the time, so I didn’t make a ticket.

The way I fixed it was to copy the function _ **manually** _, ie, recreating it.  
Saved, deleted the original, saved, copied the one I just made to the old name, saved, and deleted  
the copy.

It was a pain but I was back in business.

It was also inconsistent, I wasn’t sure what I had done to make it happen.

---

<div class="post-metadata">

**Author:** ![Banderson](https://www.epiusers.help/user_avatar/www.epiusers.help/banderson/32/50875_2.png) [@Banderson](https://www.epiusers.help/u/Banderson)\
**Post date:** [June 12, 2023, 3:25pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/3 "2023-06-12T15:25:34Z")

</div>

> [@klincecum](#):
>
> The way I fixed it was to copy the function _ **manually** _, ie, recreating it.

Yeah, not doing that. It’s working…

At some point, I’ll try to explore under the hood and see if I can find the bug… but I’m not quite desperate enough for that.

And frankly, if you (@klincecum ) haven’t yet, it must be harder that I think it is to do that…

---

<div class="post-metadata">

**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\
**Post date:** [June 12, 2023, 3:31pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/4 "2023-06-12T15:31:32Z")

</div>

> [@Banderson](#):
>
> haven’t yet

No, I was busy, and needed it done now. Only happened to me twice.

Got too much actual work at the moment.

---

<div class="post-metadata">

**Author:** ![Banderson](https://www.epiusers.help/user_avatar/www.epiusers.help/banderson/32/50875_2.png) [@Banderson](https://www.epiusers.help/u/Banderson)\
**Post date:** [August 12, 2025, 1:55pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/5 "2025-08-12T13:55:53Z")

</div>

Ok. Bumping this because it’s happening to me again and it’s annoying the crap out of me. Anyone have any ideas how to fix this?

---

<div class="post-metadata">

**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\
**Post date:** [August 12, 2025, 1:59pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/6 "2025-08-12T13:59:39Z")

</div>

> [@Banderson](#):
>
> Anyone have any ideas how to fix this?

Comment out the function code. Delete the signature and save.  
Close the editor. Reopen, recreate the signature, and save, then uncomment your function code and save.

I have also had success by commenting out the code, saving, then exporting the library and reimporting it with force, and then uncommenting the code and saving.

---

<div class="post-metadata">

**Author:** ![Banderson](https://www.epiusers.help/user_avatar/www.epiusers.help/banderson/32/50875_2.png) [@Banderson](https://www.epiusers.help/u/Banderson)\
**Post date:** [August 12, 2025, 2:45pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/7 "2025-08-12T14:45:04Z")

</div>

On prem for the win!

So whatever is looking at the signature for the syntax check isn’t looking at the same thing as the one on save. This is a screen shot after I fixed it, but if you move things around, the ParameterID and Order aren’t the same number, which is understandable. However, the syntax check was getting the field order from the parameterID instead of the order, so it was giving you an error, when it doesn’t really have one since the compiler uses the order (like it should). So I adjusted the parameter IDs to match the order number, and now the error goes away.

 ![image](https://www.epiusers.help/uploads/default/original/3X/1/4/141b76a2ad009c349bde91b4782c371df89b59a5.png)

Now. how the heck do I present this to support and actually have it work through as a bug???

---

<div class="post-metadata">

**Author:** ![Banderson](https://www.epiusers.help/user_avatar/www.epiusers.help/banderson/32/50875_2.png) [@Banderson](https://www.epiusers.help/u/Banderson)\
**Post date:** [August 12, 2025, 3:38pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/8 "2025-08-12T15:38:32Z")

</div>

ok, I submitted a ticket. We’ll see where it goes from here.

---

<div class="post-metadata">

**Author:** ![jgiese.wci](https://www.epiusers.help/user_avatar/www.epiusers.help/jgiese.wci/32/51553_2.png) [@jgiese.wci](https://www.epiusers.help/u/jgiese.wci)\
**Post date:** [August 12, 2025, 4:19pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/9 "2025-08-12T16:19:47Z")

</div>

I feel like this one they can’t deny is a bug. It’s very reproducible. Honestly I would have expected it to be fixed by now, but I just tested it in 2025.1.10 and it’s still borked.

I created two functions in a library.

- func1
- 
  - input1 (string)

- 
  - input2 (string)

- 
  - input3 (int)

- func2
- 
  - input1 (string)

I took input3 and moved it to the second spot so the arguments were then (string, int, string).

func2 code is

```csharp
this.ThisLib.function_1("test", 12, "test");

```

and it freaks out that it _ **can’t convert int to string** _

LAME!

---

<div class="post-metadata">

**Author:** ![hmwillett](https://www.epiusers.help/user_avatar/www.epiusers.help/hmwillett/32/93207_2.png) [@hmwillett](https://www.epiusers.help/u/hmwillett)\
**Post date:** [August 26, 2025, 2:51pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/10 "2025-08-26T14:51:58Z")

</div>

Adding a data point to this.  
I had this same issue, but my ParameterID and Order values _were_ the same.

I added a second parameter that is a string, but was getting an error saying it cannot convert String to Bool.

I went into the DB and switched the DataType from System.String to System.Boolean, refreshed my function, then switched it back to System.String, refreshed my function again and then it worked. 🤷‍♀️

```auto
UPDATE Ecf.EfxFunctionSignature
SET DataType = 'System.Boolean' /*'System.String'*/
WHERE SysRowID = '45DE4DB5-9ED7-42D1-87EE-B34500F0EB0A'

```

---

<div class="post-metadata">

**Author:** ![Banderson](https://www.epiusers.help/user_avatar/www.epiusers.help/banderson/32/50875_2.png) [@Banderson](https://www.epiusers.help/u/Banderson)\
**Post date:** [August 29, 2025, 3:10pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/11 "2025-08-29T15:10:08Z")

</div>

![Fun Dancing GIF](https://media2.giphy.com/media/v1.Y2lkPWU5MGVkYmEzcHFpcTVnZjFtZXdpNW44dWFrdnI4Z3p6NWo5cXdxcDhwc25raHhyZSZlcD12MV9naWZzX3NlYXJjaCZjdD1n/13hxeOYjoTWtK8/giphy.webp)

 ![image](https://www.epiusers.help/uploads/default/original/3X/6/c/6c69f87fd6ff78d3638906b9f60a58c1b3b7cada.png)

I actually got something through support! Without even a meeting to explain it!

I wish we could hot fix it, but at least we have access to the back end for a ~~reach~~ work around.

Now to understand what 12.2.100 translates to. 🤔

---

<div class="post-metadata">

**Author:** ![JMPCONJ](https://www.epiusers.help/user_avatar/www.epiusers.help/jmpconj/32/76359_2.png) [@JMPCONJ](https://www.epiusers.help/u/JMPCONJ)\
**Post date:** [August 29, 2025, 3:18pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/12 "2025-08-29T15:18:01Z")

</div>

> [@Banderson](#):
>
> what 12.2.100 translates to

2028.1.5 👹

EDIT: We’re on 11.2.400.11 which is 2023.2.11 - so might 12.2.100 be 2024.2?

---

<div class="post-metadata">

**Author:** ![Ernie](https://www.epiusers.help/user_avatar/www.epiusers.help/ernie/32/69401_2.png) [@Ernie](https://www.epiusers.help/u/Ernie)\
**Post date:** [August 29, 2025, 6:31pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/13 "2025-08-29T18:31:12Z")

</div>

12.0.100.11 = 2025.1.11 (current SaaS version)

I AM GUESSING HERE…

12.2.x is probably 2026.1 (May/June 2025 release), since 12.1.x is likely 2025.2 (October/November 2025 release)

---

<div class="post-metadata">

**Author:** ![Banderson](https://www.epiusers.help/user_avatar/www.epiusers.help/banderson/32/50875_2.png) [@Banderson](https://www.epiusers.help/u/Banderson)\
**Post date:** [August 29, 2025, 6:37pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/14 "2025-08-29T18:37:31Z")

</div>

> [@Ernie](#):
>
> I AM GUESSING HERE…

I wish we had a tag for @epicor here! See how confusing your version numbers are? The best we can ever get is an educated guess. Everyone hates it!

---

<div class="post-metadata">

**Author:** ![Mark\_Wonsil](https://www.epiusers.help/user_avatar/www.epiusers.help/mark_wonsil/32/51594_2.png) [@Mark\_Wonsil](https://www.epiusers.help/u/Mark_Wonsil)\
**Post date:** [August 29, 2025, 6:50pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/15 "2025-08-29T18:50:10Z")

</div>

~~The only~~ One place that lays it out is on the Kinetic Download page on EpicWeb:

[Kinetic Downloads](https://epicweb.epicor.com/products/kinetic-erp/Downloads/on-premises/downloads-kinetic)

Under Releases:

 ![image](https://www.epiusers.help/uploads/default/original/3X/6/9/69a64d426a375ec8782160b4c174c5dc3ae8c889.png)

See Carlos’s better answer below.

---

<div class="post-metadata">

**Author:** ![aosemwengie1](https://www.epiusers.help/user_avatar/www.epiusers.help/aosemwengie1/32/95533_2.png) [@aosemwengie1](https://www.epiusers.help/u/aosemwengie1)\
**Post date:** [September 1, 2025, 12:07pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/16 "2025-09-01T12:07:59Z")

</div>

> [@Mark\_Wonsil](#):
>
> lays it out

That’s only for already released versions. Does not help you guess on the future versions.

---

<div class="post-metadata">

**Author:** ![carlosqt](https://www.epiusers.help/user_avatar/www.epiusers.help/carlosqt/32/477_2.png) [@carlosqt](https://www.epiusers.help/u/carlosqt)\
**Post date:** [September 1, 2025, 12:14pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/17 "2025-09-01T12:14:59Z")

</div>

There is a KB in epiccare for that KB0119789  
It’s updated with the upcoming version 2025.2

## Comparing Versions of Kinetic/ERP, UX, Ice, .net and Edge Agent

> **[EpicCare Login - EpicCare](https://epiccare.epicor.com/epiccare?id=epiccare_kb_article&sys_id=28db130a97c9a2907989d414a253afa3)**

 ![image](https://www.epiusers.help/uploads/default/original/3X/8/8/883c5101b909228b4dc80a2bd532de9f85bf0fe5.png)

---

<div class="post-metadata">

**Author:** ![JasonMcD](https://www.epiusers.help/user_avatar/www.epiusers.help/jasonmcd/32/22326_2.png) [@JasonMcD](https://www.epiusers.help/u/JasonMcD)\
**Post date:** [September 3, 2025, 2:51pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/18 "2025-09-03T14:51:04Z")

</div>

> [@Ernie](#):
>
> 12.0.100.11 = 2025.1.11 (current SaaS version)

12.0 ?! What is that? There was no 11.0.

And 2025.2 is 12.1 ???

I have been game for defending the numbering, but come on now, they’re just toying with us now.

I still don’t get why 2025 is 12 anything and not 11.4.

Ugh. Going to yell at that cloud now.

---

<div class="post-metadata">

**Author:** ![carlosqt](https://www.epiusers.help/user_avatar/www.epiusers.help/carlosqt/32/477_2.png) [@carlosqt](https://www.epiusers.help/u/carlosqt)\
**Post date:** [September 3, 2025, 3:20pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/19 "2025-09-03T15:20:48Z")

</div>

> [@JasonMcD](#):
>
> I still don’t get why 2025 is 12 anything and not 11.4.

The reason is [Linux on SaaS FAQ For Cloud Customers (Kinetic 2025.1)](https://epicweb.epicor.com/resources/MRCBynder/MFG_Kinetic_Cloud_2025.1-Linux_Container_FAQ-Customers.pdf)

---

<div class="post-metadata">

**Author:** ![Chris\_Conn](https://www.epiusers.help/user_avatar/www.epiusers.help/chris_conn/32/93797_2.png) [@Chris\_Conn](https://www.epiusers.help/u/Chris_Conn)\
**Post date:** [September 3, 2025, 10:58pm UTC](https://www.epiusers.help/t/function-signatures-for-syntax-check/103913/20 "2025-09-03T22:58:19Z")

</div>

Let me in on this ride.

 ![image](https://www.epiusers.help/uploads/default/original/3X/f/9/f971c64b97fb7006d8a8529c6f6c6b1b745c9776.png)
