Forum Discussion

RZidaj's avatar
RZidaj
Regular Visitor
3 months ago
Solved

Dataflow Gen2 Mashup Error

Error Code: Mashup Exception Expression Error, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: Expression.Error: We cannot convert a value of type Table to type Text. Details: Reason = Expression.Error;ErrorCode = 10276;Value = #table({"Value"}, {});Microsoft.Data.Mashup.Error.Context

 

I'm creating a new dataflow and I keep getting hit with this error. the problem is I'm not sure which step is causing it because when I run this query in pbix it works fine but it doesn't work as a dataflow


I think the problem might be at this step but I don't know how to resolve it as I need the data to come through as a table under the Issues field so that I can expand it and view the columns

 

 

 

CICD
data hub
  • v-achippa's avatar
    v-achippa
    3 months ago

    Hi RZidaj,

     

    Thank you for reaching out to Microsoft Fabric Community.

     

    Here looks like the issue is related to Dataflow Gen2 handling the Issues column as text during the refresh, while the function is actually returning a table.

    So please try explicitly keeping the column type as table and avoid returning null. Please try this below query:

    Table.AddColumn(#"Filtered Rows", "Issues", each try fnGetAllIssues([Project Key]) otherwise #table({}, {}), type table)

     

    Also please check and remove any automatic changed type step for the Issues column if present.

     

    Thanks and regards,

    Anjan Kumar Chippa

9 Replies

  • v-achippa's avatar
    v-achippa
    Community Support
    3 months ago

    Hi RZidaj,

     

    Thank you for reaching out to Microsoft Fabric Community.

     

    Here looks like the issue is related to Dataflow Gen2 handling the Issues column as text during the refresh, while the function is actually returning a table.

    So please try explicitly keeping the column type as table and avoid returning null. Please try this below query:

    Table.AddColumn(#"Filtered Rows", "Issues", each try fnGetAllIssues([Project Key]) otherwise #table({}, {}), type table)

     

    Also please check and remove any automatic changed type step for the Issues column if present.

     

    Thanks and regards,

    Anjan Kumar Chippa

    • RZidaj's avatar
      RZidaj
      Regular Visitor
      3 months ago

      Thanks so much Anjan!

       

      Your suggested query returned the result (all rows). Unfortunately I pressed the solution button a bit too quick and I'm still getting the same mashup error when selecting save & run 

      Error Code: Mashup Exception Expression Error, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: Expression.Error: We cannot convert a value of type Table to type Text. Details: Reason = Expression.Error;ErrorCode = 10276;Value = #table({"Value"}, {});Microsoft.Data.Mashup.Error.Context =

      • RZidaj's avatar
        RZidaj
        Regular Visitor
        3 months ago

        I'm wondering if this could be the problem step

        I've just updated it to this below but it's also still returning the same error

        Table.FromList(Source, Splitter.SplitByNothing(), {"PRs"}, #table({}, {}), ExtraValues.Error)
         
  • stoic-harsh's avatar
    stoic-harsh
    Super User
    3 months ago

    Hey RZidaj,

    If you want the 'Issues' column to contain a nested table that you can later expand, use a row-context filter explicitly.

    Example:

    Table.AddColumn(
    #"Filtered Rows",
    "Issues",
    each
        try
            Table.SelectRows(
                fyleDetails,
                (x) => x[Project Key] = [Project Key]
            )
        otherwise
            #table({}, {})
)
    This returns a proper table per row. Then you can safely expand 'Issues'.

    Your current expression is effectively returning:

    • sometimes a List
    • sometimes a Table
    • sometimes null

    Power BI Desktop tolerates this more than Dataflows do.

    Dataflows require stronger type consistency during cloud refresh. In the updated expression, now the column is always a 'table' type.

    Best,

    Harshit

    • RZidaj's avatar
      RZidaj
      Regular Visitor
      3 months ago

      Thanks for explaining this to me clearly While your suggested query returned a different result than I was expecting (it returned only a single row of result as opposed to all rows) it helped me understand where my problem was

  • lbendlin's avatar
    lbendlin
    Super User
    3 months ago

    Your "otherwise" branch needs to return a table stub, not null.