Collection showing as Variable instead of Table

(1) Share

Report

Posted on by Gargoolgala

270

Hi,

I have an app where everything was working fine. I deleted a Dataverse table and imported an updated version - I made sure all columns are the same etc.

As soon as I did that I noticed an error. A Collection is showing as causing a problem - on deeper scrutiny I noticed that the Collection is showing as a Variable instead of Table.

Anyone know why this might be happening - I changed no code at all and the code in error is based on 5 tables in a Switch - I only updated 1 of those tables. The error starts at the Switch level stating it has some invalid arguments. If I change the collection name in all the appropriate spots the error goes away until I run it and then it returns the new collection to a Variable instead of Table.

Something seems to have corrupted.

See below - TempDataAscTemp1 is not a table.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

ronaldwalcott 3,847 Super User 2025 Season 2 on at

Like (0)

Report

Show the error in the Switch statement.

How do you initialize the collection in the app? If this isn't done properly you can run into trouble if data structures it depends on are changed.

Did you try saving and republishing the app?

1 people found this reply helpful.

Was this reply helpful? Yes No
Gargoolgala 270 on at

Like (0)

Report

Hi ronaldwalcott,

you prompted me to revert to an old version as it seemed that today a new PA version was pushed by MS.

It is now all working - for now. I will see what happens when MS force the latest version on my app again.

Let's hope it was simply a glitched upgrade by MS - grrrrr.

Was this reply helpful? Yes No
ErikM9 163 on at

Like (0)

Report

As ronaldwalcott stated, it explains my issue.

I made the mistake of changing a column type in SharePoint. Now my app is littered with errors.

I've gone through the app to make sure that all values are text and not just number, as it was originally. But that didn't do the trick.

Though, when I recreate the collection but, under a new collection name, that works.

Was this reply helpful? Yes No