Show all references to a collection

[AnthonyPhan]

There is currently no way in powerapps to display or search where collection is either defined, used or indirectly used. This can make debuging an app with many objects very difficult. This Idea is to have a feature which will display all references to a collection in the same way that is currently available for global variables. 

[Audrie-MSFT]

@GregLi added as FYI

[KroonOfficeSol]

Great Idea to do so. I have cases that I want to change/delete a collection at all places off my app for example when I want to rename a collection to a more descriptive name.

It would be easy to do this when you can change the name at the ClearCollect formula, then go to the collection screen, select the old collection, go to each instance off where the collection is used, change the collection name there and done

btw, this is what I do when I want to change a local or global variable.

Greatings,

Paul

[MikeLockwood]

Any update on this, it has been under review for over 6 months.

[Jennie]

I also have this exact problem at the moment. any updates?

[Darvin]

I would like to see this update as well. It's very difficult to change the schema of a collection, when you need to manually rename all its references throughout the app. The ability to see all collection references would also allow developers to easily drop and recreate a collection.

[DE1]

This is needed. You forget where all the code is, such is the nature of PowerApps

[flarebear]

I'd like a more general approach to searching within the codebase of a PowerApp. If the code that is hidden behind the properties of all UI controls and could be dumped to a single file, the code within the file could then be searched for any objects of interest such as collections or anything else within the code. It would also provide a means for tracking deltas between different versions of a PowerApp. Right now, the inability to search easily within a PowerApps codebase is a major inhibitor to serious adoption as it means maintenance of a PowerApp is already impaired before a line of code has been written. The problem only gets worse as the number of screens within a PowerApp increases thereby increasing the search-space. [Update 31st Oct 2019]. I've found that it is possible after all to edit the code outside of the PowerApps studio. See https://powerusers.microsoft.com/t5/Building-PowerApps-Formerly/Search-code/m-p/135849