Classic Sunset Officially at 2026.1

[JMPCONJ (John Magee)]

@hmwillett

Classic may be approaching sunset, but the dawn will be there the next day.

Sure, the sun might come up the next day…but will APR still work?!

[hmwillett (Hannah Willett)]

@JMPCONJ

but will APR still work?!

Anything is possible with some

[JMPCONJ (John Magee)]

Well played…and a good way to end the day.

[Mark_Wonsil]

Going back a few years (April, 2008!!!), came up with some lyrics myself, sung to Hotel California:

@system

Hotel Vantage-Vista

On Gore’s superhighway, cooling fans in my ear
Warm smell of disc-drives, rising up through the air
Up ahead in the rack-space, saw some flickering lights
My head grew heavy and my sight grew dim
Must stop coding for the night

There they stood in the doorway;
I heard the Controller yell
And I was thinking to myself,
‘This could be a dot Net or DLL Hell’
Then they fired up the client and they showed me way.
They said “Those arn’t bugs up there…
…we designed it that way.”

Welcome to the Hotel Vantage-Vista
Such a lovely screen (Such a lovely screen)
Costs lots of green.
Need plenty of RAM at the Hotel Vantage-Vista
In about a year (In about a year)
We’ll have that feature here.

The code’s really-twisted, it sometimes abends
They got some pretty tools - they call BPMs
They program in C-Sharp, sweet Redmond sweat.
Some code they remember, some code they forget

I asked the System Manager,
‘Please run this on Wine’
He said, ‘We haven’t had stability here since Windows of 99’
And still that process is calling from far away,
A Web Service in the middle of the night
…we started earlier that day.

Welcome to the Hotel Vantage-Vista
Such a lovely Grid (Such a lovely Grid)
Why’s that columns hid?
We’re livin’ it up at the Hotel Vantage-Vista
What a nice surprise (what a nice surprise)
My session’s still alive…

Mirrors of the disc drives,
Version eight is on ICE
I think ‘We’re just prisoners here, of our own advice’
With the Progress Explorer,
They prepared to delete
They stab it with their Escape keys,
But the process did not decease.

Last thing I remember,
the record was modified before
Had to restore the user back
To the way she was before
‘Refresh,’ said support man,
‘We’re trained to defeat.
You can add as much as you like,
But you can never delete!’

[klincecum (Kevin Lincecum)]

@Mark_Wonsil

sung to Hotel California:

I posted mine…

[Mark_Wonsil]

@klincecum

I posted mine…

Don Hendley said if I ever sang it again, he’d sue me like the rest of the Eagles.

[JasonMcD (Jason McDermott)]

I know I have said this before, but that seems to be the theme here so…

• We have been 100% browser since January. We lived.
• OK; the users are 100%
• I am 100% browser when possible, and I really mean that - I do not take the “easy” road. Yes, uBAQs on my version can only be done in classic, as well as Functions and BPMs are just buggy in the browser. But I make all other BAQs in the browser and do all other work and testing in the browser as well.
• We have tons of integrations and dashboards and queries. Sure you (whoever you are reading this) have so many more, yes, great, you are better than me. But I guarantee whatever is the critical mass for “a lot” we have hit it too.

People, software does advance! You cannot be surprised by this.

I can’t stand WinForms. I am very happy to not look at them again.

[Ernie (Ernie Lowell)]

@JMPCONJ

but will APR still work?!

It will WORK, as the underlying stuff is all the same.

Whether or not you can MODIFY it might be up for grabs…

[ajyoung11 (Andy Young)]

We’ve been Saas for a couple years now and have more than half our users on the Browser version of Forms. One thing i still recommend users go to classic for, is mass grid/list updates. I was reminded of how bad it is in the browser, when I helped enter tags for Inventory this weekend. We’re entering thousands of tags. In classic you just enter a count and hit enter and move to the next tag. You can do a row per second and classic keeps up with you. The browser can’t handle it. It takes much longer to process each row. I really hope they come up with a solution for that in the next 1.5 years.

[mccoyjf (Jim McCoy)]

I’m somewhere in the middle on this. I still get frustrated when I find a limitation, (perceived or actual) when working in App Studio. But, I’ve recently been pulled into working on a classic forms project and I must say that I’m getting to the point where working in App Studio is more enjoyable. So perhaps I’m starting to get there.

[aclements (Andrew Clements)]

There is definitely an issue with inner sub queries in a baq, causing invalid column names errors in the server log when used in a kinetic dashboard.

I’ve replicated the issue on 2 dashboards, where the baq runs ok directly.

I’ve raised it with Epicor and will put an update on here when resolved.

[klincecum (Kevin Lincecum)]

@aclements

There is definitely an issue with inner sub queries in a baq, causing invalid column names errors in the server log when used in a kinetic dashboard.

The issue is not with the queries, but with that wizard.

Let me see if I can find the thread.

Edit:

I'm this close to rage quitting - Application Studio and Dashboards

There is a known bug in the Basic Application Wizard where if your BAQ has subqueries, the grids get created with all columns including those in subqueries that are not in your top level. Then the way the provider model works is it runs the BAQ with a select list of columns and because of the above this can now cause the SQL error you are seeing because the columns do not exist to the top level. Therefore when this happens you need to your grid after the app has created and go to Grid Model > …

[aclements (Andrew Clements)]

Thanks - I’ll take a look today

[Randy (Randy Stulce)]

@klincecum

The issue is not with the queries, but with that wizard.

Ahh, when I uplifted our Dashboards I used @tpogue and @mbayley posted from Insights. As it has a good base structure to build a dashboard for us.

[Randy (Randy Stulce)]

@ajyoung11

One thing i still recommend users go to classic for, is mass grid/list updates. I was reminded of how bad it is in the browser, when I helped enter tags for Inventory this weekend. We’re entering thousands of tags. In classic you just enter a count and hit enter and move to the next tag. You can do a row per second and classic keeps up with you. The browser can’t handle it. I

Agreed, that is a BIG gap and I’m not sure what us users could do other than maybe a DMT?

[ajyoung11 (Andy Young)]

I’ve considered DMT, but I don’t feel comfortable opening DMT up to users. Way to high of a probability they mess something up. That’s why I send them back to classic.

[Randy (Randy Stulce)]

We don’t open up DMT either. We have Excel “templates” they fill out and we run the DMTs once we’ve looked them over. At least “downloading” an excel copy of a grid seems to be working for this process to work.

[Chad_Smith]

@Randy

Agreed, that is a BIG gap

Agreed, these seem like “small differences” in parity but could have huge impact. I do think the enter for a new row is working in 2024 browser. I do not know if it’s everywhere or depends on where. The delay in creating the new row is not insignificant however. It’s multiple factors slower.

Another example is that I think (though I am occasionally wrong) that we still can’t change the tab order of fields on a Kinetic application either. These QOL issues will have a large impact on users and amount to more than “who moved my cheese” in some scenarios.

[utaylor (Utah Taylor)]

Mark this is wild haaha back before AI, it was pure human creativity.

I can’t believe that this lyric is still relevant today:

@system

They said “Those arn’t bugs up there…
…we designed it that way.”

[kve (Kevin Veldman)]

@ajyoung11

The browser can’t handle it. It takes much longer to process each row.

I noticed this on Configurator Lookup tables. On classic, I can bring in a lookup table with 20 columns and 100 rows in about 10 seconds. It took over 5 minutes in browser.

EDIT: I put this out as an example, but it isn’t really a huge deal for PC Lookup Tables, because A) you shouldn’t be doing mass changes to Lookup tables very often, and B) there’s a handy import tool that should probably be used instead. Do you edits in Excel to the CSV and re-import.