Yes, the use of Choices from the ContentType does work and allows you to access the Name column.
The problem in our case is we need to get to the ContentType.Name on each record for a comparison for many other things that go on in the app.
Not that we couldn't change the logic to try and collect those types ahead of time with the Choices function or do lookups with the ID's to get to the names (which would work fine), it's just that, for this one app...that represents a boat load of work.
AND...this is still something that needs to be fixed. It did work once and it appears to be there, but something else is preventing it from now working properly.
Thanks for the follow-up.
This issue still exists.
Any workarounds seem to be not delegable either, which in my case makes it useless.
You can't create a calculated column in SharePoint from the Content Type name, but you can use Flow to trigger when a new file is created to populate a string column with the content type name and then filter that in PowerApps, but man alive what a hacky workaround. The flow needs loads of retry logic built in because you can't update the file properties of an open file (even though two people can simultaneously work on the same document).
Check it out!
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020
The largest Power BI, Power Platform, and Data conference in New Zealand