Sage 100

Well, that post doesn't look pretty,  See attached pdf for screen shots.

I think I have posted about this issue previously,  Sometimes I can paste a screen shot and other times it displays as a blank image,

Well, that post doesn't look pretty,  See attached pdf for screen shots.

I think I have posted about this issue previously,  Sometimes I can paste a screen shot and other times it displays as a blank image,

I ran into it with one client.  Sage released a hot fix - SO7106T.  I reached out to my client to schedule installation, but they haven't had me do it yet so I can't say for sure the fix works.  

Well, that post doesn't look pretty,  See attached pdf for screen shots.

I think I have posted about this issue previously,  Sometimes I can paste a screen shot and other times it displays as a blank image,

YES, @Jeff Schwenk .  My client also just upgraded, and it only affects one user.  I had her open a case with Sage but I do not know if they have solved it yet.

Fingers crossed...

YES, @Jeff Schwenk .  My client also just upgraded, and it only affects one user.  I had her open a case with Sage but I do not know if they have solved it yet.

If it is only for 1 user, their security profile might have been scrambled during the upgrade.

Try giving them a new Sage login.

Fingers crossed...

YES, @Jeff Schwenk .  My client also just upgraded, and it only affects one user.  I had her open a case with Sage but I do not know if they have solved it yet.

Maybe try changing their User 'Code' in User Maint from 2char to 3char (if applicable) and/or delete any bad [initial] records in sy_user via dfdm.

If it is only for 1 user, their security profile might have been scrambled during the upgrade.

Try giving them a new Sage login.

Fingers crossed...

YES, @Jeff Schwenk .  My client also just upgraded, and it only affects one user.  I had her open a case with Sage but I do not know if they have solved it yet.

hotfix worked for me.

Maybe try changing their User 'Code' in User Maint from 2char to 3char (if applicable) and/or delete any bad [initial] records in sy_user via dfdm.

If it is only for 1 user, their security profile might have been scrambled during the upgrade.

Try giving them a new Sage login.

Fingers crossed...

YES, @Jeff Schwenk .  My client also just upgraded, and it only affects one user.  I had her open a case with Sage but I do not know if they have solved it yet.

Does anyone have version 2022 hotfix SO7106T?  I have a customer that has missing customer/item invoices when doing the SO Customer last Purchase Maintenance flashlight lookup.  Tried the Rebuild and it didn't work. I'm thinking maybe the hotfix will solve it.    They have a lot of custom modifications.  Hope the hotfix doesn't overwrite any mods.

hotfix worked for me.

Maybe try changing their User 'Code' in User Maint from 2char to 3char (if applicable) and/or delete any bad [initial] records in sy_user via dfdm.

If it is only for 1 user, their security profile might have been scrambled during the upgrade.

Try giving them a new Sage login.

Fingers crossed...

YES, @Jeff Schwenk .  My client also just upgraded, and it only affects one user.  I had her open a case with Sage but I do not know if they have solved it yet.

attached...

Does anyone have version 2022 hotfix SO7106T?  I have a customer that has missing customer/item invoices when doing the SO Customer last Purchase Maintenance flashlight lookup.  Tried the Rebuild and it didn't work. I'm thinking maybe the hotfix will solve it.    They have a lot of custom modifications.  Hope the hotfix doesn't overwrite any mods.

hotfix worked for me.

Maybe try changing their User 'Code' in User Maint from 2char to 3char (if applicable) and/or delete any bad [initial] records in sy_user via dfdm.

If it is only for 1 user, their security profile might have been scrambled during the upgrade.

Try giving them a new Sage login.

Fingers crossed...

YES, @Jeff Schwenk .  My client also just upgraded, and it only affects one user.  I had her open a case with Sage but I do not know if they have solved it yet.