You go vote & comment on my Epicor idea, and convince them this is nuts and overkill.
I mean, I have access to the Db object. I can erase everything. Why in the world does it matter if I want to look at some properties, or load a class, or retrieve a file?
If you are crazy enough to write where you aren’t supposed to and you screw it up, that’s on you, not Epicor, so why do they care? Tell the dummy customer to pound sand, not take my tools away.
This is going to absolutely make my life miserable, and it doesn’t make any sense.
If there was still shared hosting with custom code, for sure, I could see it, but that no longer exists.
This is gonna be in you on-prem guys codebase too most likely, so don’t get cocky.
Well, if you have a specific use case, maybe we can think of alternate ways to pull off what you need. But as a general what can we do about this error message… Unless you know whose shins need to be whacked at Epicor, I don’t think there is any cure.
Well the one I am looking at right now parses a csv file and saves it to a UD table. Can it be done with DMT? Sure but. . . why should we have to when we already have this nice interface for it? I don’t understand Epicor’s logic in taking this away from us at all.
@aosemwengie1 Yes, all of that can be worked around.
I don’t currently have time to do it, but most of it can be found if you poke around in this post.
I have a mix of stuff in there, some allowed, some not. If you can’t piece it together, or someone else doesn’t step up, I’ll see if I can help when I get back from the beach.