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
Hi @lmeyerov - by way of an interim update, I've tested this both on my checkout (prior to updating for recent changes against master), and afterwards, and both look correct, based on the configuration from your above screenshot, e.g.:
However, I've noticed that in this case, we have Age Group in both the Source and Source node properties data roles, as well as Employment Type in both the Source node properties and Edge properties data roles, we get the value sets twice in the sourcePropertyMetadata object. As such, Power BI maps them twice in the data view, e.g.:
If I remove one of the duplicate fields from the pane (e.g. Employment Type from Edge properties), then we see one less array element here, e.g.:
Because we filter by role name when retrieving values, both of these instances overlap, and are being doubled-up (or potentially more if used in other data roles). Therefore, it's likely that I'm just not adding them in the same order that you might have done, to be able to successfully reproduce (and still cannot).
Either way, this is likely the issue and I will ensure that only the first value array is retrieved from the data view if it is assigned to multiple data roles.
dm-p
linked a pull request
Nov 9, 2022
that will
close
this issue
Notice
Age Group
andEmployment Type
below -- their values appear swappedThe text was updated successfully, but these errors were encountered: