We should really have this!
Will be handy indeed
+1 !!!!
I was going to add this idea, but obviously was added before, but I see that I am not the first one that has occurred it. Will be very very useful.
Like the feature that exists in Visual Studio.
One of the most requested ideas already:
https://www.outsystems.com/Ideas/66/conditional-breakpoint
J.Ja
Ups!
Hi,
Is possible to implement a conditional break point in debug mode. Like a visual studio and others programming IDE.
Stop on break point only the condition is accepted.
Thanks
Same as: https://www.outsystems.com/ideas/66/Conditional+Breakpoint
Add Conditional Debuging, at least in actions. For example set a breakpoint in a action and be able to insert values in the input parameters of that action to the debug stop when the values match.
Hey, man. It looks like it's a duplicate. Check this Idea
https://www.outsystems.com/ideas/66/Conditional+Breakpoint
While debugging, it should be easier to continue to a certain value when being in a loop.
ergo, conditional breakpoint?
A conditional breakpoint would be great!
Sometimes we need isolate data for a specific behavior helping to find an error/bug/diff rule.
But to find this data extra effort are necessary looking for debug row-by-row.
Can be implemented a feature to break condition, like VS have.
It would help to debug lists iterations if there would be a conditional stop not stop on every loop. For example If I want to look into specific loop where say id=99 and there is a foreach with 1000 records and I don't want to alter the flow to have possibility to stop only when value in a loop is 99. otherwise I have to click through 98 loops and do not miss the one I need to look into.
Hello,
I believe this is a duplicate from https://www.outsystems.com/ideas/66/Conditional+Breakpoint
Kind regards,
Márcio Menezes
+1
Also useful for me, sometimes I only want to stop execution when a given condition verifies in my code.
Please make sure that the future conditional breakpoint can not only have variables having a certain value but also can have expresions where variables must be between 2 values or break on multiple values. Just like is normal in MS .NET development studio.
We really need this!
I am in a situation where i desperately need this right now, clicking through 800 records to find the one I need is ridiculous. 8 years this thread has been open, and nothing. This should be a top priority for the dev team.
Hey Michael,
Thanks for the feedback! We are actually evaluating a useful MVP in the short term, stay tuned.
Out of curiosity, were you searching for in that loop? What would be the condition? ID = XX? NAME = ?
Cheers,
Hi everyone!
It would be great to have a functionality in debugger that could allow us to go to a specific ID of the iterated list while debugging For each loops, like a "continue or jump to Something.ID=..."
Sometimes we have a specific error that we want to screen for some ID's while others are behaving as expected in the loop.
Having something that could allow us to continue to ID for instance 5, that we know that is behaving correctly, and then compare with ID 9, that is having a weird result, would easy the process of error correction.
It would also avoid us to run all Id's (namely in large loop actions) until desired ID, then jumping to the folllowing one.
You mean a conditional breakpoint? (check out this idea.)
Not properly. I would like to beak all time in order to screen errors in all process, but to skip some of the loops or doing only a few of them
Yeah, I think Sam is right, this is called conditional breakpoint and I think this idea can be merged with the one Sam linked.
Hey Helena,
The way we see this happening is by setting in fact a condition on your breakpoint (something like ID = XX).
Will merge the ideas!
This Idea is from 2010, Does anyone know if it will be implemented soon?
Not yet Martin. When it's implemented the status will change to "Implemented" like this one
Hello
I would like to be able to do a conditional debugging.
What do i mean by that is if i have a timer running 500000 records and there is one that have a problem and i know his code or Id i would like to be able to tell to the debugger to stop in that break point only when "id = 401 or id = 502".
Now a days i can do this by adding an if with that condition and an assign with break point.
If possible i would like to have an if statement in the break point so i can choose when the break point will trigger.
eg 1: if(true) -> normal break point
eg2: if(a.id = 22)
eg3: if(getuserid() = 50 and Round(pointer) = 5)
I am wondering why such popular & useful idea isnot implemented yet even after 9 long years?
What 9 years, you made me scroll up again to confirm. This is what developers love to have. OutSystems should implement this long ago.
There should be an option to add conditional breakpoint for ease of debugging. This is specifically usefull in case of long loops or conditions where we are getting issue on specific point. So this conditional breakpoint will help to pause at the breakpoint only when certain condition is matched.
There is simillar conditional breakpoint option available in Visual Studio for implementation reference.
This idea can be merged with existing idea that has already more than 300 votes
https://www.outsystems.com/ideas/66/conditional-breakpoint?IsFromAdvancedSearch=True
Oh yes, but I was not able to find it in matching ideas while adding this idea. Even when I use same name to add idea it shows some crazy suggestion but not relavent one. Looks like something is wrong with this marching idea feature. See below image
Would be interesting, in the debug, if we were able to choose in wich for each iteration we want to stop. Or maybe have a way to jump to the 25th iteration...
I would like to be able to put a break in the debugger when a variable changes. So the debugger will suspend the execution of threads like the Break On All Exceptions option when the value is changed.Maybe when watching a variable this could be an extra option.This could save some time when a variable is changed but you don't know exactly where.Of course it would be even better combined with conditional breakpoints.Then it would be possible to break anywhere in a module when a variable has a specific value.
It would be good if we could have a way to add Conditional Breakpoints.
We could add this kind of breakpoint and then set a condition for service studio to stop.
If the condition is True then the break-point will stop else the break-point would be ignored.
Thanks,
Luis
Wow, this Idea is nearly 10 years old! (And still not implemented)
I gave up on it. It might be that whats in Visual Studio obvious functionality will never make it in OutSystems Service Studio. What kind of service is that?
So, today I have a query which returns items from ~200k entries, each entry having about 10 linked entries each. There was an error in the data for the linked entries.
Conditional breakpoints would have allowed me to narrow down the query parameters and outliers in the data much faster. With conditions, I could split the resultset and / or stop only when certain variables are set to certain values - you know the drill.
If-branch copy-paste application-logic modification horror (with editable condition values from site property) got me through, but what a mess... Also, publishing twice to set/unset each "breakpoint" was so slow I almost got overtaken by a glacier.
Chrome offers this for javascript, can we please have this feature to server side debugging as well?
We need this, guys. Debugging with conditional breaks is a must. At least once per week (if not more) I have to add IFs to the code in order for the debugger to stop where I want it to stop.
Consider there is a bigger loop of record list. and while iterating it becomes tedious to keep pressing continue until the required enumeration is reached sometimes there is a possibility to miss. Hence will it be possible to add a conditional breakpoint so that the debugger will stop when the given condition is meet
It is a good idea but already sugested
Consider to merge it
Regards
I would really like this.
As a workaround, I added one additional if to the code with my condition and then empty assign to the true branch, so that if the condition is met then it will also go to an assign branch that will trigger the debugger. To visualise this approach:
Please add this! It is a nightmare to debug over big lists. The option of Mr. Potter obviously works, but it would be nice to do this without having to add something to your code, create a new version and having to update the consumers.
When debugging code, it would be interesting to be able to add a condition for the breakpoint, based on the data available in the running action.
It would be nice to have a conditional breakpoint while debugging. It is useful when we don't want to loop many times through loops, we could have the debug stop when some some condition is met like, for instance, variable x = 37 or any other number.
Having the option of setting some conditions on breakpoints could really help in scenarios such as; iterating through a list and knowing you want an index at the end of the list,
You could apply breakpoint and have it only become active once that condition is fulfilled
For example when List.CurrentRowNumber = (List.Length-1)Once this condition has been hit the breakpoint would become active, otherwise it'll will sit deactivated
Hi All,
A very important feature that I would like to have available when debugging my applications, would be to have the possibility of having breakpoint's that stop according to a condition defined by the programmer.
Is particular useful when you search for a specific use case in your logic and for example imagine a loop with 2k records. If you need to stop only when the record code is 'xpto' you need to iterate all records or a part of them, to see the record that you need. The workaround is implementing an "if" on my logic, but requires change the logic.
Thank you.
Great Idea Gonçalo!
This would be very useful!
same as https://www.outsystems.com/ideas/66/conditional-breakpoint?IsFromAdvancedSearch=True
Hi Rebecca Hall,
True :)
It Will be merged, but is a reinforcement of this need.
It would be great if you could set debug as conditional.
Example: In a list from 0 to 10 the debug stops only in 7.
It would be great indeed, many people think alike, for that this is one of the oldest ideas created already in May 20210. I will merge your's into the existing idea.
will be very much helpful. i was about to post it, but found this idea already on radar. :)
Please! Please!! Please!!Talking about some solutions related here, for example: Use a site property + dummy assign with normal breakpoint, this is not convenient 'cause sometimes we have to solve a prd issue in a fast way and if we had a way to interrupt the code based on a condition in the first moment and based another conditional in the second time is VERY BETTER.. We can't stop the code, change the site property then start again...this is not pratical solution.
I would like to see the feature where breaking point hit the code flow only on specific conditions instead of hitting it every time.
We have this functionality in many IDE's when it comes to traditional development but I would love to see this feature in OS IDE and it also saves lot of time while debugging the piece of code in loops.
Best Regards,
Gandeev Boddeti
Yes very useful idea indeed