cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Microsoft
Microsoft

Refreshing a data source does not pull in new fields

I extended one of our views to include a few more fields.

PowerApps does not see them.

Refreshing the data source does nothing to expose them.


I think I'm going to have to resort to deleting and recreating the data source.

1 ACCEPTED SOLUTION

Accepted Solutions
Super User III
Super User III

Hi @pitr

 

I think this is a bug - there have been several reports of this behaviour in the past few weeks. If what you're working on isn't urgent, this seems to clear itself if you wait long enough.

Here are a couple of posts with further information/suggestions.

https://powerusers.microsoft.com/t5/General-Discussion/Powerapps-don-t-show-new-fields-from-Azure-SQ...

 

https://powerusers.microsoft.com/t5/General-Discussion/Refreshing-SQL-Server-Schema-in-PowerApps/m-p...

 

 

View solution in original post

17 REPLIES 17
Super User III
Super User III

"Extended one of our views"??  PowerApps does not pull from views (unfortunately). It pulls from the list.

So, if you added the field to the list definition, it should be there on a refresh.

Also, make sure the field you are looking for really exists by what you are looking for (i.e. the names do not always match what you expect).

If ever in doubt on a field's real name - go to the list settings in SharePoint and edit the column.  Then, look at the end of the URL in the browser - it will show you the "real" name of the field.

 

Hope it helps.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up. Solved your problem? - Click on Accept as Solution. Others seeking the same answers will be happy you did.
Check out my PowerApps Videos too!

I should clarify:

The data for the PowerApp is stored in SQL, not SharePoint.

The PowerApp currently uses views for all reads.

 


I do see the new fields when I query the view correctly.

Ah...yes!  Good clarification! Smiley Happy

 

Are you using a data gateway or Azure SQL?

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up. Solved your problem? - Click on Accept as Solution. Others seeking the same answers will be happy you did.
Check out my PowerApps Videos too!

Azure SQL

To there I end my friend!  I have nothing meaningful to advise.

Perhaps your instinct of removing the source and then adding it back would be the solution.  I know that seems to be the case when we deal with Flow signature changes.  Possibly the same issues.

Good luck.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up. Solved your problem? - Click on Accept as Solution. Others seeking the same answers will be happy you did.
Check out my PowerApps Videos too!
Super User III
Super User III

Hi @pitr

 

I think this is a bug - there have been several reports of this behaviour in the past few weeks. If what you're working on isn't urgent, this seems to clear itself if you wait long enough.

Here are a couple of posts with further information/suggestions.

https://powerusers.microsoft.com/t5/General-Discussion/Powerapps-don-t-show-new-fields-from-Azure-SQ...

 

https://powerusers.microsoft.com/t5/General-Discussion/Refreshing-SQL-Server-Schema-in-PowerApps/m-p...

 

 

View solution in original post

Thank you all!

Remove and re-add did not help, so I'll just try to wait it out.

I'm working with an on-prem db via gateway. Deleting & re-adding the connection didn't work. Adding a new table which was a rename of the original didn't work. I just made a new database with my renamed columns and am repointing / rebuilding from there.

Having this issue at this Very moment, never had this issue before today.

On-Prem SQL Server

Added a New field to a table.

added New field to old View used by Flow

would not find new field in view

ended up creating a test field in the view itself to test, found that test column fine.

set New field alias to same as test field alias, flow returned New Field content with test field alias fine

Set alias of New Fieldto original column name, now flow complains about missing a column (test field)

 

sigh

Helpful resources

Announcements
secondImage

Experience what’s next for Power Apps

Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.

Power Apps Community Call

Power Apps Community Call: February

Did you miss the call? Check out the Power Apps Community Call here.

New Power Super Users

Congratulations!

We are excited to announce the Power Apps Super Users!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

Top Kudoed Authors
Users online (55,237)