You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a mark property is bound to aggregated data, we currently produce a new dataset if a new groupby field is introduced or amend an existing dataset for new summary fields. However, if additional transforms (e.g., filter, formula) are added to an aggregated dataset, the above logic will fail to transfer the transforms over.
A naive approach to copying transforms over, however, will fail because the schemas of the two datasets may not be equivalent. Consider this flow:
User binds groupby fields A & B and a summary field C.
User adds a filter transformation using B.
User unbinds B from the mark.
User binds groupby field D.
The text was updated successfully, but these errors were encountered:
When a mark property is bound to aggregated data, we currently produce a new dataset if a new
groupby
field is introduced or amend an existing dataset for new summary fields. However, if additional transforms (e.g., filter, formula) are added to an aggregated dataset, the above logic will fail to transfer the transforms over.A naive approach to copying transforms over, however, will fail because the schemas of the two datasets may not be equivalent. Consider this flow:
A
&B
and a summary fieldC
.B
.B
from the mark.D
.The text was updated successfully, but these errors were encountered: