Is anybody able to successfully paste-new in kinetic sales order entry? Using the client, paste-new gives this error:
Using the browser it works fine. This is in 2021.2.29. Support refuses to troubleshoot since it works in the browser “it must be environmental”.
I just tried this in the desktop Live and Pilot clients. Both at v11.2.200.0 (2022.2.3*) I went to an existing sales order, selected a release row, copied selected, then went to the …waterfall menu and clicked PasteNew. After a delay, the new release was pasted in without error.
Having said that… I never use the desktop client kinetic anymore. So many times, folks here have said ‘oh, that doesn’t work in the client, use the browser.’ So, I just stopped using the client. Why did they even put effort towards producing a desktop client if it was already kneecapped? The browser version works fine, and dev tools are a big help.
(* seriously guys, pick one version method and stick with it, this is cray!)
Ok if you don’t mind would you test it with lines? We are doing paste-new on the lines grid.
We can’t use the browser because we use classic for everything BUT sales order entry.
Paste New also works on lines. Perhaps when you get bumped up to 2022 this bug will go away? Why don’t you still use the classic sales order entry? I guess you’re doing the right thing and trying to get started in kinetic. We stick to classic forms for business critical tasks. But if you want to do any real work, save yourself the headaches and use the browser version. Once your people get used to it, it’s not that bad. As a developer, I often have both the client and the browser versions open, as we can only do some developer things in the client. Even then, I use the classic forms over the kinetic forms. If I need to do anything kinetic it is in the browser.
Long story, thanks for your testing. Since it works in the browser in 2021.2 I don’t think going to 2022 will fix this in the client. Just frustrating not to know what is causing the client issue.
Finally figured this out, paste insert doesn’t work with net tcp, only https binding.
Thank you for figuring this out and saving me the agony today.
On a tangent, I am really annoyed with being stuck on net.tcp. We don’t want to use that, but we have to since Epicor cannot handle a public SSL with a wildcard domain or a .local domain (since they don’t exactly match the cert). Also why we are on 2021 and not 2022.
Can’t wait to learn what other pitfalls there are with net.tcp in Kinetic.
We had numerous problems with kinetic and net tcp, meaning the kinetic interface - classic didn’t seem to care. It became so problematic for us that I switched everyone to use https now. If you are still using shell home page/classic ui it may be fine for you.