Method General Q & A

Re: Action Breaking

Jack — Fri, 03 Jun 2016 20:40:30 GMT

I found a particularly interesting anomaly that I thought you should be aware of.

It appears that I can undo the bug on the QLI Price Calc button's onclick event (the one that makes conditional statements empty and un-deletable) by taking a particular version in the Quotes Details App (Version 12 or Version 10, same screen, different version number) and making it the main, "Live for all users" screen and then copying the screen, choosing to make a copy without redirect. The result is a screen with one version that has working, normal conditional statements, even though the screen it was based off of did not. Please note that this does not solve the issue inQLI Hidden Update, only QLI Price Calc.

Just for additional info, the BREAKING EVENTS screen was a copy of Quote Details Version 10. ANOTHER BREAKING EVENTS screen was a copy of Quote Details Version 11, which is a version off of 10 with changes to nothing having to do with the QLI Price Calc (except maybe for calling its action set).

I am sticking with Method for now, but can you see how all of this can get really irratating and confusing to keep track of? To help, I HIGHLY RECCOMMEND ADDING THE FEATURE TO PUT NOTES TO A VERSION ASAP. This will help me greatly in terms of managing versions, like in this case.

Re: Action Breaking

Jack — Fri, 03 Jun 2016 18:02:38 GMT

I found it, but it turns out it indeed was on another screen and version. The BREAKING EVENTS was a copy of the quote details screen. The Quote Details Screen had the additional issues, so I created a copy again and this time they appear. The new screen (same app) is ANOTHER BREAKING EVENTS. the buttons with hte buggy events are in the top left.

Re: Action Breaking

Jack — Fri, 03 Jun 2016 17:42:43 GMT

I thought there was, in QLI Price Calc, but it all apeears to be working fine, as least on this screen and version.

Thank you for the update Ben.

Re: Action Breaking

Method_Ben — Fri, 03 Jun 2016 17:27:44 GMT

Hi Jack,

Sorry to hear you are having further issues with the platform. Thanks for bringing this up with us!

I took a look at the Actions on the QLI Hidden Updates Button as you mentioned, and can certainly see the issues you are describing. Are you noticing other issues on this screen at all? I took a look over a few of the other actions and nothing jumped out, but theres a lot happening on this screen so I may have missed something.

We will continue to investigate this one on our end, and ill report back with anything we find.

Terribly sorry for the Inconvenience Jack!

-Ben

Action Breaking

Jack — Fri, 03 Jun 2016 01:23:46 GMT

After making some changes to a screen I have not customized in a while, I noticed an error where there previously was not one just hours before when entering data through via the screen. Something I had not touched in months has broken. Several conditional statements are blank and cannot be removed, an "update controls on screen" action is totally blank and an "insert records in table" action wont even let me view it without popping up error messages before it finally is just blank. All this stuff was working, and I do not know why it is not any more. The reliability of this platform is now a subject in my company, and the current support for customized screens is as minimal as possible, putting us in get-over-it-or-leave situation.

This is not the first time things like this has happened, but, until now, it has been a much better usage of my time to eat the loss, redo everything and move on than it is to try to isolate the issue, report it, leave it as is and still find a way to continue development. This case however is the biggest set of fails on one event that I have ever found.

The screen is now called BREAKING EVENTS in the Quotes app.

The click event of the button QLI Hidden Update is the event that is messing up. It can be found at the top left of the screen, in the first section.

I have qalso gotten this error threee time today alone. I have no idea what I am doing to get it, but after losing all my progress and doing the exact same things again, I can finally sucessfully save my changes.