I knew .NET 6.0 for the server, but is that now true for the client? I didn’t think they were going to invest in that upgrade since the client is going away.
1 Like
I tried it again a few minutes ago. It then updated instead of the error message. However, after the update when I double click the icon nothing happens.
I checked the event viewer:
Ah - not 100% sure, I never did a client install for that version outside of the server so I didnt notice.
But I do seem to remember seeing pre-req for 4.8 in install guide.
2 Likes
And I believe Olga mentioning that if you’re doing server-side development (Directives, etc.) then you’ll need .Net 6 at the client. But I think the client itself is still 4.8 Framework and not Core.
2 Likes
No, you don’t need .NET6 on client, it should work fine, as I am told
2 Likes
This was the post I remembered. It may be required for people using code?
Kinetic 2022.1.1 Transaction Scope - Kinetic 202X - Epicor User Help Forum (epiusers.help)
Here is error on logon, it is not related to any code issues that can happen later. It is more missing or outdated locked dll issue.
2 Likes
Reloaded the client folder - which got me into Pilot
2 Likes
I don’t have any information on the initial error being reported here. But I do want to add some clarity as there seems to be some confusion with the platform.
.NET 6 was introduced in 2022.1 (server only). There are no major platform changes in 2022.2 so the server remains on .NET 6 and the client remains on .NET Framework 4.8.
Developing custom code (method directives, etc.) does not require .NET 6 on the client. If it is installed, it will take advantage of it for code validation. But if it not installed, it will gracefully fall back to using .NET Framework 4.8.
3 Likes
In Kinetic - searching for PO Suggestions - you need to scroll down to bring in all of the records.
After you have them all and select all - still not allowing you to bring in all of the records you want to review.
Only the first 200
Interesting. The reason I mentioned it was this reply from @Jonathan from the above link about Transaction Scope:
So if I understand correctly, it should gracefully fall back. If one still has trouble with code validation, then it doesn’t hurt to install .NET 6.
1 Like
To my knowledge Epicor Auto-Update was never good at updating the Client for Major Versions. You may need to make sure you re-download the latest 11.2.200 Client.
I am making an assumption you relied on Auto-Update, perhaps you didnt.
Also I run Epicor.exe and not Kinetic.exe for success.
4 Likes
So if I understand correctly, it should gracefully fall back. If one still has trouble with code validation, then it doesn’t hurt to install .NET 6.
Correct, there is no harm in installing .NET 6 on the client. If it helps with some scenario then go for it. For the most part, you should be fine without it.
3 Likes
Yes, it appears the auto-update bricked the install. Got it working now
2 Likes
For PO suggestions - it is very common to pull in alot of data into the “workbench” to select to promote to a purchase order.
The idea is not to export the data, but use the standard process in Kinetic to manage all of the suggestions.
Right now, will be required to used the classic process to work with the suggestions.
2 Likes
Bruce,
I am curious how the classic process actually works. Are they:
-
Pulling in all suggestions across all suppliers? A group of suppliers? One supplier? (I’m assuming by Buyer)
-
How many suggestions are converted to orders per day? Or per Run Purchase Suggestions?
-
Do they review the entire list or just Select All and convert to orders?
It is my understanding Epicor will allow a 5K row limit, isn’t 5K enough? I guess batching it in 5K groups.
@LarsonSolutions Can you elaborate on this? Perhaps in a different post as I guess it’s off topic. I searched the forum but don’t see it mentioned. I mean, I know what the periodic posting is, but what do you mean by eliminating it?
Santiago I did notice issues with having .NET Core Runtime on my PC. Even Epicor aside, for example I use LINQPad and suddenly I got
The type initializer for 'Epicor.Data.EpiDataContext' threw an exception. because Serilog could not be found in Epicor.Hosting.dll (Inner Stack).
I removed .NET 6 Runtime from my PC and long and behold, all is back to normal.
I think .NET 6 should supplement .NET 4.7 but what happens it actually breaks stuff when compiling code on the PC arghhhhh! Its not an Epicor issue, just a .NET Backwards compatibility issue.
Even tho I had NuGet specific packages for EntityFramework, somehow .NET 6 Runtime messed it up.
Now I can explain this too 
Basically - Remove .NET 6 Runtime from your Client PC and all your BPMs and issues will be resolved and you wont have to include some special assembly in your BPMs.
2 Likes