Hi Team, I noticed a potential bug in PBI Service. In the Query Editor of PBI Desktop, I'm merging a table multiple times with two other tables (overall 6 merges, first two tables are web sources, third table is an xml-file retrieved from a local drive). Each merge is performed as a new table and the final table is a reference to the last merge step. Refreshing works in Power BI Desktop, but when uploading and refreshing the semantic model in PBI Service, I'm receiving different error messages - sometimes even resulting in our Gateway going offline. Pls. find an error message example below: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Evaluation ran out of memory and can't continue."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}}],"exceptionCulprit":1}}} Table: xxx I've found a workaround by unchecking "enable load" of all intermediate steps, only enabling load for the final table. Nonetheless, comparing to other queries that we already did it doesn't seem reasonable that loading the merge-steps into the model should result in crashing the gateway. I hope you can help with this issue. Thanks!
... View more
