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
- Looks for unique values across source and destination data roles, and ensures that only distinct entries are included in the nodeFile
- For source and destination properties, the row matching the first discovered index is used for values, to prevent property arrays potentially being ragged and causing server issues
Commit d3e4aed re-works the nodeFile entries to work better here. This will resolve both issues discovered during reproducing this on my machine:
If the source or destination data roles contain many repeating values (which will be common for Power BI), these are resolved to the distinct entries across both
For unique entries, the first discovered location in each array is stored, and then used for subsequent lookup of source and destination properties from the dataset. This avoids issues where the combination of properties results in more rows for each combination of source and destination (which would result in arrays of a ragged length for properties)
@dess890, hopefully your test should now look similar to the following if you update your branch:
anything added to the src/node properties results in 0 nodes and 0 edges?
The text was updated successfully, but these errors were encountered: