cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Huzar44
Frequent Visitor

"Missing source field in the schema" error when changing dataflow refresh from manual to automatic

Hi,

I have a dataflow that works perfectly fine when triggered manually. When I switch the refresh setting to "Refresh automatically" I got following errors:

Missing source field cr2c4_zawartosc in the schema

Missing source field cr2c4_zawartoscoczekiwana in the schema

Missing source field cr2c4_zawartoscskorygowana in the schema

That are three floating point number type columns in the table, which do exist in the table. I can see that the data is loaded correctly when I trigger manual refresh.

 

In order to solve this problem I have tried to:

1) load the data to a new table with the same columns - same issue

2) add new columns to existing table with decimal number data type instead of floating point number

3) change the precision of columns from 4 to default 2

4) recreate the dataflow from scratch

 

Unfortunately without success. Does anyone have an idea what to do with this issue?

Full error report attached.

 

1 ACCEPTED SOLUTION

Accepted Solutions
Huzar44
Frequent Visitor

To whom it may concern. Together with support I found a workaround for my Problem. The root cause was the mapping of percentage column type from query to decimal column type in target table. After changing the type from percentage to decimal in the query, project validation does not report "missing columns" error anymore. Illogical but true.

View solution in original post

2 REPLIES 2
EricRegnier
Super User
Super User

Hi @Huzar44,

You have tried everything I would have suggested... Unfortunately Dataflows errors message and logs are very limited. I would submit a Microsoft Support Ticket to get more info at: https://admin.powerplatform.microsoft.com/support

Let us know how that goes... 

Huzar44
Frequent Visitor

To whom it may concern. Together with support I found a workaround for my Problem. The root cause was the mapping of percentage column type from query to decimal column type in target table. After changing the type from percentage to decimal in the query, project validation does not report "missing columns" error anymore. Illogical but true.

View solution in original post

Helpful resources

Announcements
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

M365 768x460.jpg

Microsoft 365 Collaboration Conference | December 7–9, 2021

Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.

Users online (2,245)