Thanks Ben, I just used Quick Edit to add a row of data to my empty Sharepoint list and it appears to have fixed the problem.
Adding a record to a list to make sure it is not empty is not a solution or a fix for this! A list being empty should not throw an error - and it never used to until a few days ago. An PA update has caused this bug and it needs to be fixed.
Yes, a work-around has been provided, but there are many business cases where a list will/should be empty and having to have the list populated is not a solution.
Please can a proper fix be applied to resolve the bug?
Adding a dummy record did the trick for me. Though I really think that Office365 should be able to cope with empty lists. The "faulty" setup did work for a while and this error has only started to appear recently. As clunky as Sharepoint 2013 was at least it didn't have the random changes/bugs that 0365 seems to provide me with almost daily. Sigh.
@dhock Where we need to go to put it on their radar? 'Cause to a client it just means that Powerapps App are crushed - in an end analysis it means that the Power User just do a trash job
Featuring samples like Return to the Workplace and Emergency Response Applications
We're excited to announce our first cross-community 'Can You Solve These?' challenge!
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
We are excited for the next Super User season.
Features releasing from October 2020 through March 2021