Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I merged two tables. They each have underscores and dashes in their name. The resultant merged table now has underscores in some field names. When I try now to match that new field with another, I get a DAX syntax error message pointing to, not the whole column name, but just up to the first dash.
I tried renaming the column before referencing it in DAX but that apparently doesn't work. I see "Expression.Error: A cyclic reference was encountered during evaluation" but it does not indicate where this cyclical reference is.
code (changed var/table/file names) -
let
Source = Table.NestedJoin(#"table_with-underscores_and-dashes.tsv",{"RawGUID"},#"other-.tsv",{"GUID"},"other-",JoinKind.LeftOuter),
#"Expanded other_table-with_underscores-and_dahses" = Table.ExpandTableColumn(Source, "other_table.tsv", {"GUID", "Date", "url", "StringToCheck"}, {"other-.GUID", "other-.Date", "other-.url", "other-.StringToCheck"}),
#"Filtered Rows" = Table.SelectRows(#"Expanded other-", each [#"other-.StringToCheck"] <> null and [#"other-.StringToCheck"] <> ""),
#"Filtered Rows1" = Table.SelectRows(#"Filtered Rows", each [StringToCheck] <> null and [StringToCheck] <> ""),
#"Renamed Columns" = Table.RenameColumns(SameLabeles,{{"other-.StringToCheck", "stc"}}),
#"SameLabeles" = Table.SelectRows(#"Renamed Columns", each Comparer.Equals(Comparer.Ordinal, [StringToCheck], [stc]))
in
#"SameLabeles"
Solved! Go to Solution.
AH so the issue is that earlier in the code I referenced "SameLabeles" (in #"Renamed Columns") and then I declare #"SameLabeles". Why can't powerBI point this out?
AH so the issue is that earlier in the code I referenced "SameLabeles" (in #"Renamed Columns") and then I declare #"SameLabeles". Why can't powerBI point this out?
Hi @tb__,
>>When I try now to match that new field with another, I get a DAX syntax error message pointing to, not the whole column name, but just up to the first dash. I tried renaming the column before referencing it in DAX but that apparently doesn't work.
How do you match that new field with another? And what your DAX looks like? Could you please share more details for further analysis?
Best Regards,
Angelia
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
108 | |
100 | |
78 | |
64 | |
58 |
User | Count |
---|---|
148 | |
111 | |
94 | |
84 | |
67 |