Application Studio, corrupted events

Anyone else having their events corrupted after adding another control?
I get something significant working save the layer and then commit. I come back and add another button and the last event I worked on that has nothing to do with the new button is missing a chunk of the actions I just “confirmed” working. If I restore that history layer and verify the event in question is back to the way it was when I did the commit all looks good. As soon as I add the new button that same event is corrupted again. I saw the post about having more than one event open at a time when saving/commiting and made sure that was not the case.

This happened twice before and the only way around it was to rebuild the event after adding the new control. NOT ACCEPTABLE, what a waste of my time. Can we back charge Epicor for our wasted time for a product that is not ready for release?

Has anyone else seen this, is it a known issue?
Did you find a way to keep it from happening?
Are there any fixes for this in 2025.1?

Dazed, Confused and Disgusted :scream::scream::scream::scream::scream:

5 Likes

Hey Mike,

Unfortunately you’re not alone, myself included :sob:

4 Likes

Only every day.

3 Likes

Yes, I’ve had this happen to me more than once. I’ve had whole Layers go corrupted too the point I had to delete and rebuild them.

2 Likes