Microsoft recently updated its API's to default to version 2.0.
I have custom API's built in Buisness central SaaS.
Here is the AL code for this example I am having the issue with
![bignadad_0-1721934134021.png]( "bignadad_0-1721934134021.png")
Here is my testing in postman.
I can force schemaversion 1.0 in the url and the Type Enum is correct "Put-Away"
![bignadad_1-1721934196938.png]( "bignadad_1-1721934196938.png")
When i switch to schemaversion 2.0 you can see I get the unix encoded value for the Type Enum "Put_x002D_away"
![bignadad_2-1721934251139.png]( "bignadad_2-1721934251139.png")
The problem is my Power BI dataflow will not allow me to force the schema to 1.0
Here is the error I am getting in Power Query when trying to view my dataflow
---------- Message ----------
DataSource.Error: Dynamics365BusinessCentral: Request failed: The remote server returned an error: (400) Bad Request. ('Put_x002D_away' is not an option. The existing options are: ,Put-away,Pick,Movement,Invt. Put-away,Invt. Pick,Invt. Movement CorrelationId: ce628306-bbf1-4e10-97e6-3f2d42e96f8b.)
In the first step I have tried to replace that "_x002D_" with "-" but it still fails
Table.ReplaceValue(#"Sorted rows", "_x002D_", "-", Replacer.ReplaceText, {"type"})
Here is the advanced editor data
let
Source = Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, [UseReadOnlyReplica = null, AcceptLanguage = null, ODataMaxPageSize = null, Timeout = #duration(10, 0, 0, 0)]),
#"Navigation 1" = Source{[Name = "PRODUCTION"]}[Data],
#"Navigation 2" = #"Navigation 1"{[Name = "*** Machine LLC"]}[Data],
#"Navigation 3" = #"Navigation 2"{[Name = "Advanced"]}[Data],
#"Navigation 4" = #"Navigation 3"{[Name = "***/BI/v1.0"]}[Data],
#"Navigation 5" = #"Navigation 4"{[Name = "registeredWhseActivityHdr", Signature = "table"]}[Data],
#"Sorted rows" = Table.Sort(#"Navigation 5", {{"systemCreatedAt", Order.Descending}}),
#"Replaced Unicode dash" = Table.ReplaceValue(#"Sorted rows", "_x002D_", "-", Replacer.ReplaceText, {"type"}),
It seems as though the Power Bi Business Central connector hasn't been updated to accomodate this new schema version.
What's even more odd is I have other dataflows that are still refreshing without errors. They also have these unicode values.
![bignadad_3-1721934644229.png]( "bignadad_3-1721934644229.png")
