I've learned recently about using default values as a workaround for when a 0 is returned by an API. In simple response mode Pabbly will display a 0 and in regular mode, pabbly will show a null value when an API returns False for a value. The problem is that in simple mode, the value really isn't 0 and is very misleading.
In the workflow I shared in my tasks history ID field - I've set up a demonstration of this. We get the results from the API, which returns false for disabled. Pabbly displays 0 as the value and then actually uses this 0 value in the filter in step 3 as the filter is set to only pass if that value exactly equals 0. Then in future steps, it won't pass on the 0 value to the spreadsheet. A value of 0 is fundamentally different, but it seems they are being treated as the same thing. When Pabbly displays the 0 as it does in simple mode, this is a visual queue used in future steps and is misleading. If the value is null, it should show as blank like it does in the non simple response mode. The example workflow I shared should not be passing the filter because the value of that field is not 0.
Thanks for your help.
In the workflow I shared in my tasks history ID field - I've set up a demonstration of this. We get the results from the API, which returns false for disabled. Pabbly displays 0 as the value and then actually uses this 0 value in the filter in step 3 as the filter is set to only pass if that value exactly equals 0. Then in future steps, it won't pass on the 0 value to the spreadsheet. A value of 0 is fundamentally different, but it seems they are being treated as the same thing. When Pabbly displays the 0 as it does in simple mode, this is a visual queue used in future steps and is misleading. If the value is null, it should show as blank like it does in the non simple response mode. The example workflow I shared should not be passing the filter because the value of that field is not 0.
Thanks for your help.
