Sage 100

If they use VI imports from an ODBC source, wait until PU1.

Wayne,

I gave them some "feedback" on my case that brought the KB freeze to light... Of course nothing real will come of it, but it felt good to vent a bit.

>Of course nothing real will come of it

I wouldn't say that. Sage seemed aware of the issue. From what I heard it got caught in the transition from old kb to new kb. If we keep up the pressure to improve this eventually Sage will get tired of hearing about it and we may see some action.

@Kevin Moyes Do we have enough to talk with Sage KB / City  about to create a monthly informal 30 minute meeting? Something like 3rd Wed of each month.

If they use VI imports from an ODBC source, wait until PU1.

Wayne,

I gave them some "feedback" on my case that brought the KB freeze to light... Of course nothing real will come of it, but it felt good to vent a bit.

Wayne,

(I like Jeff's idea of a "v2023 issues" thread and don't want to take it fully off the rails for general Sage complaints).

Perhaps start a discussion for KB / portal / support issues, and see what comes up? (We have a long list of gripes, but who @ Sage would listen?  ...not the Dev. team for sure... not their area...).

>Of course nothing real will come of it

I wouldn't say that. Sage seemed aware of the issue. From what I heard it got caught in the transition from old kb to new kb. If we keep up the pressure to improve this eventually Sage will get tired of hearing about it and we may see some action.

@Kevin Moyes Do we have enough to talk with Sage KB / City  about to create a monthly informal 30 minute meeting? Something like 3rd Wed of each month.

If they use VI imports from an ODBC source, wait until PU1.

Wayne,

I gave them some "feedback" on my case that brought the KB freeze to light... Of course nothing real will come of it, but it felt good to vent a bit.

This just in from Sage U yesterday.  They now offer an overview of v2023.1.  I thought the PU release was just bug fixes.  Did they release an elearning session on v2023 as well?<o:p> I would think that is the important one.</o:p>

<o:p> </o:p>

Wayne,

(I like Jeff's idea of a "v2023 issues" thread and don't want to take it fully off the rails for general Sage complaints).

Perhaps start a discussion for KB / portal / support issues, and see what comes up? (We have a long list of gripes, but who @ Sage would listen?  ...not the Dev. team for sure... not their area...).

>Of course nothing real will come of it

I wouldn't say that. Sage seemed aware of the issue. From what I heard it got caught in the transition from old kb to new kb. If we keep up the pressure to improve this eventually Sage will get tired of hearing about it and we may see some action.

@Kevin Moyes Do we have enough to talk with Sage KB / City  about to create a monthly informal 30 minute meeting? Something like 3rd Wed of each month.

If they use VI imports from an ODBC source, wait until PU1.

Wayne,

I gave them some "feedback" on my case that brought the KB freeze to light... Of course nothing real will come of it, but it felt good to vent a bit.

I haven't looked at the Sage U version yet but the YouTube left me inspired by the two new features and thinking (a) when will our journey to MFG be over and (b) Hmm, I don't remember but I guess there is a Paperless Office Conversion Utility - I better look at that - and sure enough it's in *UTL and used for pre-2018 upgrades where paperless was used for JC or PR. Who knew ( note me ). 

This just in from Sage U yesterday.  They now offer an overview of v2023.1.  I thought the PU release was just bug fixes.  Did they release an elearning session on v2023 as well?<o:p> I would think that is the important one.</o:p>

<o:p> </o:p>

Wayne,

(I like Jeff's idea of a "v2023 issues" thread and don't want to take it fully off the rails for general Sage complaints).

Perhaps start a discussion for KB / portal / support issues, and see what comes up? (We have a long list of gripes, but who @ Sage would listen?  ...not the Dev. team for sure... not their area...).

>Of course nothing real will come of it

I wouldn't say that. Sage seemed aware of the issue. From what I heard it got caught in the transition from old kb to new kb. If we keep up the pressure to improve this eventually Sage will get tired of hearing about it and we may see some action.

@Kevin Moyes Do we have enough to talk with Sage KB / City  about to create a monthly informal 30 minute meeting? Something like 3rd Wed of each month.

If they use VI imports from an ODBC source, wait until PU1.

Wayne,

I gave them some "feedback" on my case that brought the KB freeze to light... Of course nothing real will come of it, but it felt good to vent a bit.

Installing 2023.1 to a brand new Sage 100 2023 upgrade where I have not migrated any data and only have ABC company. The Now merging dictionary files. This may take a few minutes --- is certainly taking a few minutes. I'm surprised at the time it's taking because I have no live customer data in the system yet. It's also possible that this customer's malware/av is causing a problem. FWIW.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------