Sage 100

TIL, if you've sold a customer on 100c "" upgrade "" and they are BIE users, they should expect to continue using the classic interface or the BIE views will not display. This seems as if something Sage has known about for some time. Via: https://support.na.sage.com/selfservice/viewContent.do?externalId=78517&sliceId=1

Looks like changing from Standard to Classic to Standard is recommended to fix. We are testing.

Legacy VI Jobs don't appear to work with Classic either. Frustrating! Had the same issue with BI Views too and the changing of the interface did take care of it.

Haven't gone too far into BIE yet. One user reports it didn't fix.

User did log out of Sage and log back in correct?

They claim ..

@NancyHanson - What legacy VI's don't work with Classic? Back when v2016 hit the street, I stayed with the Classic view for a very long time because the PR VI would not work in Standard view. They have since fixed that issue. Do you really have issues running legacy VI in CLASSIC? What version of Sage and what PU? Std or Advanced. FWIW, I have user in Sage 100c v2016 running via an RDP connection that BIE is failing to display the records. It works for other users on same RDP server so I suggested that IT blow away her profile and start over. Waiting to hear back now on whether a change to Classic will work for her. Seems a shame that a primary selling point of 100c does not work...

I just realized I indicated the wrong desktop originally. VI didn't work with Standard. I'm checking with the client on the job, might have been an export job. They only own JC & PR for legacy. Version 2017.1 Std. Error was 'Data Files are not setup for Company LAU'. There is a write up and fix for 2016.1 and I believe I tried to install it on my local to 2017.1 (for giggles!) and it wouldn't let me. Advised her to change back to Classic, assumed it worked as she didn't respond.

Amazing....... I haven't installed the office v2017 as there wasn't that much sizzle to make it worth my while.

I'm confused about the views to which you are referring? Are you saying they don't work in the new Standard UI? Mine work fine on my laptop with 2017.1

Mine also appear to work on 2017.2