Skip to main content
Quality of Life enhancement: for the transform task in a bionic set up (JO or Rules), if you drop a field into the GroupBy section, it will change all fields to an aggregate. However, I constantly drop a field in there on accident, thinking its the Filter section (muscle memory from rule building). This means that I have to remove the field, which changes that field back to non-aggregated data point. But all others remain aggregated.



I don't know that I care which of these happens, or if there are better suggestions, but my thoughts are:




  1. Pop an alert box that says "are you sure you want to drop something here?"; it could get annoying, but it will save me time nonetheless


  2. IF I remove all fields from the GroupBy section, reset all fields in the Show Me back to a non-aggregated data point







Just to be clear how frustrating this is, I created this post after I did it. I then immediately went into the same rule and did it again.



Please make my life easier!


Option #2 would be best - I would get annoyed by having to confirm each time I drop something in Group By.


Hi Christopher,







I am just wondering how it would be if someone genuinely added a group by and wanted the fields to be aggregated and then removes the field from group by. In that case, changing the show fields from aggregated to non-aggregated might not be a good idea.



What are your thoughts ont his ?



Regards,



Jitin


Terms & ConditionsCookie settings