Function Library disabled after upgrade 2022.1.18 to 2023.1.10

Kinetic ERP
1

Upgraded test environment to 2023.1 and I have a function library with 18 functions in there that is disabled and I cannot enable it. Function has been working for a year in production environment. I can delete the function and reference to IssueReturn and save it. Worst case I have to create a new library just for this function, just will be a pain with about 40 widgets and custom code in this function.

The type ‘JobHeadRow’ exists in both ‘Erp.Contracts.BO.IssueReturn, Version=11.2.300.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992’ and 'Erp.Contracts.BO.JobEntry, Version=11.2.300.0,

2

Edit: I’m stupid hold on.

3

I thought we were going to have less of these issues not more :rofl:

First, try referencing the full names of the type, and see if that fixes it.
Otherwise you may have to make a workaround.

4

More often than not it will come to this. This is a major pain point no doubt.

5

I don’t think you can reference the full type in Widgets and Variables. I tried using “Other” and selecting the service to see if the full name would populate. Dang it.

6

Ahh widgets, the bane of my existence.

I would break my workflow into 2 (or an appropriate number) of functions then.

7

It’s time to start reporting these as bugs, if y’all aren’t already.

The same types should not be defined in more than one assembly.
One place, one reference.

8

This was reported as a bug back in Epicor 9. It never went anywhere it technically isn’t a bug is just a poor design choice. You can have the same type defined in different DLL’s as long as you reference them via an Alias

Its a dumb choice.. but its a choice.

9

I’m aware, but I’m gonna be an a** until they submit to my will.

10

You mean widgets broke on upgrade?!
oh-my-shocked1

You can fix this with custom code
giphy1

11

ah, this again…