I’ve run into this problem intermittently in the past and it seems to be happening with regularity now. I’ve working in Application Studio 2024.1.5, and have an SaaS client and an on-prem client, occurring with both of them.
When I’m doing anything outside the simple things in Application Studio, it seems like pretty regularly my Save and Publish seem to just stop working. If I’m not getting the blue bar at the top swiping across, I know I’ve lost it, and any further changes are lost. I can close out of the app, get back in and resume my work in application studio again. But, I’m back to save early/save often, to ensure I’m not making a bunch of changes that I have to redo.
It seems to happen more when I’m in and redoing events. I had it happen last week (cloud install) when I took a fairly simple event and added quite a few more conditions and dialogs (changing from a proof-of-concept event to one that had all the edits/hooks in it). After the first time of losing a good hour or two of work, I noticed that when I don’t get the blue bar, I’ve lost the ability to save. Probably took me 4 or 5 times before I got all my changes in. It’s happening again now (completely different on-prem install) when I’m in renaming buttons and the associated events.
When looking at your connectors, if you ever see one without an arrow at the end, you’re in trouble. But just delete the connector and add it back. Also, If you add a connector on something like a condition, make sure to set the connector as true or false.
What I figured out when it was happening to me was that if it is not saving, there is something wrong with your customization. One time when it happened, I had forgotten to enter something in a trigger field (one of the below). Once I fixed it, it saved. I would review everything you did to make sure you didn’t miss something.
That’s probably it then. I had a button click event where it called a function. Everything worked great. So, I went back in and added a bunch of dialogs - one at the front with an “Are you sure”, a dialog if they said NO, a dialog after the function call (one on a Success, one on a function error), then added a couple other functions (grid refresh, slider close).
I couldn’t save, so I’d exit and come back in, and half my widgets were gone. I’d readd them a few at a time and save. I assumed (wrongly) if there was an error I’d get some type of message, not simply throw away my changes. First time it happened I saved and closed, no warnings I was losing all my changes.
My warning for others: Save Early/Save Often. If you don’t see the BLUE BAR across the top when you save, then it must be as John said - an error somewhere.
I was doing a lot of development on the very first releases of Vantage 8.03. In those days, you did a lot of interim saves because you never knew when it was going to blow up on you. This brings back memories.
The problem that I have run into is working on a BAQ - a lot of time put in and I need to take a break, but I can’t save my work because there’s an error.
Let me save the BAQ (or other code) and put a flag on the object saying “error”.
