Just another thought, sometimes we try to do too much in one function making the routine less cohesive. For example, why should Epicor take on the job of reading Excel files? Why take on that dependency? Instead, you could write a regular ASP.NET core function that does that work and in turn posts to a Kinetic Function that updates Kinetic. Now I have two functions that are easier to test and diagnose when problems arise. I am not introducing an extra dependency into Kinetic. I could even use that import Kinetic Function for sources that are not Excel.
The reasoning is in this post.