I am talking about the Design SSRS workflow. Its laid out in the help. The workflow you are describing works for simple report modifications but is not practical for complex custom report development.
Got it. I’ll go research. Just trying to get up to speed.
Well this is fascinating, I sure have never seen this before.
I didn’t follow through today, but I’ll try this next time I get an SSRS report request.
So I see now, it’s not “Report Style”; it’s a new complicated process.
That is to say, it takes like 8 steps to get to here, but once you do, it gets closer to the rapid changes like I used to do in classic.
So you get NO visible errors when you upload? OK yeah, eek!
That means your ssrs design menu item which is under processes is set to launch in classic.
Oh right, yes it does require the edge agent to work, but it doesn’t require the classic client. The edge agent just has to point to the right app server.
Got it.
Just trying to feel your pain.
No offense (OK a little) to all the on-prem people on here who are still avoiding opening a web browser, but we ALL need to be ready for 2026.1, and it behooves ALL of us to help get the parity gaps ironed out ASAP. Yeah, we can delay adoption for 2 years, but we need to report the problems now, and support people like @aosemwengie1 who (unfortunately) are the volun-told beta testers.
I am too but modifying and troubleshooting reports in Kinetic is a huge PITA compared to Classic.
I created it when I worked for a different company. I went back in and voted for it after I took that screenshot lol.
Ohhh. Well OK. You win this round.
This is the way. I do all this but step 5. I just go all in with the testing on the actual menu instead of pressing the generate kinetic form. Having the errors show up in the classic error screen is great. When the classic upload works but the menu report doesn’t, the system monitor is a great place to see what I missed. All I want is the functionality of the classic report upload in kinetic and I will be happy.
Me too, that is literally all I have asked for for the last 3 years. Shot down every single time.
Yeah, @aosemwengie1 isn’t reporting (pun!) this issue to us all because she likes some stupid way of doing things. As the title says, she decided on a whim to give another shot at the soon-to-be ONLY way of doing this, and it’s still miserable.
We all really need to pay attention to these posts. “Can’t see it from my house” is not going to last much longer, people.
I tried this the whole way through today.
[Note to self: “I said I would be less negative…”]
OK, so… one thing I found is that you can only upload an RDL (aka “Publish”) once per Download/Design. That’s annoying.
In classic I left the file open. I’d make a tweak or two, then upload and test, then tweak/upload/test, ad infinitum.
Now it’s “Download” > “Design” > tweak > “Publish” > test > Download AGAIN > Design AGAIN > etc.
Other randomness
For me, I thought Report Builder was not launching. Turns out the server popup was hiding behind other windows. Had 4 of them till I noticed. 
Is there a place to change the download folder (“local location”)? I guess it’s moot once you actually notice the popup… But I just have a habit of keeping the RDLs somewhere I can find them.
Also, I need to replicate the error thing as you started out with in this post, in order to also report it. [I am trying to be good.]
You use preview, that part is 100% the same as it worked in classic. Once you publish you are done.
The popup from report builder is also exactly the same as it has always been.
The part where you can’t set the download location is annoying, but just bookmark a shortcut to the extremely deep folder where they hide them and then its not too much of a hassle.
Hmm. So I followed the guide, which says (6) save, (7) exit, (8/9/10) Publish.
But you do “Preview” while testing, and NOT Publish? I am trying but I get nothing with that.
- The Connect to Report Server dialog box displays. If you are designing the report on the server, enter the Report server URL and click Connect. If you are designing the report on your local machine, click Cancel.
- Make changes to your report. For this example, you update a couple labels to use the bold style.
- Save the custom report.
- Exit Report Builder.
- Return to the SSRS Report Design application.
- Select the Overflow menu and Publish.
- The Publish Report Definition panel slides on, asking if you want to override the SSRS Report Definition with you new .rdl file. Press Yes. This overrides the .rdl definition in the report folder you created on the server.
Well yeah, but it never used to hide so well. It’s not on the task bar when it first comes up and it pops under the browser window. It’s livable, just wanted to warn others. It takes after the EAC regenerate data model design. Well that was at least on the task bar.
Ohhh. That’s what they are saying:
I guess I should ask what you pick here. I said cancel as I thought it was local.
SaaS can’t connect to the SSRS database so we have to select Cancel.
Yeah, that’s a bit annoying but how Windows works I guess.