Dataverse unexpected behavior / column does not exist

(0) Share

Report

Posted on by Dev's Dev

Hi everyone,

I was trying to build a flow for a data export from Dataverse. Three of the columns are lookup columns, so I add the column names to the "Expand" parameter in the List Rows action.

This has never given me issues in previous flows. The logical names are used and are spelled correctly. What's more is that the contents of the lookup columns become available as dynamic content when I'm creating the flow, indicating that they do exist and I am referencing them correctly.

What's also odd is that you can see the icon for Dataverse is broken. Many of my connectors are also experiencing similar metadata breaks.

Is anyone else experiencing similar issues today? Am I doing something wrong or differently in this case? Could it be related to the Microsoft blackout that happened earlier today? Or is there another explanation?

Please let me know if you have any thoughts!

-Dev

Categories:

Microsoft Dataverse

Tables

I have the same question (0)

All responses (1)

Answers (0)

Michael E. Gernaey 51,223 Super User 2025 Season 2 on at

Like (0)

Report

Dataverse unexpected behavior / column does not exist

Hi @David Abu

Last night, at the Hackathon, I was coaching something through something that used Dataverse. She went right to the table and grabbed the column name, I was looking right at it with her.

And our flow would not work because it tossed the same error as you, so yes I saw it last night.

We did not have time, but what I asked her to do was add a listing of rows from that said table, so we could look at the data to see what Flow thought its name was, but she is supposed to reach out to me today, as I wanted her to be 100% certain it was the right environment and Table version etc, however I do not like coincidences that you saw it same as we did..

Was this reply helpful? Yes No