to be able to have different powerapps forms for different content types in sharepoint list. so that all can merge into a single item.
Thank you for this idea. Although this is not currently on our roadmap, we invite the community to continue voting on this feature as we consider feasibility for upcoming releases. @KeremY
What are you actually trying to achieve? Because if you ask me this is already possible with some creative hacks in mind.
I managed to achive this with tabs in powerapps then giving Admin rights to specific tabs. Also used the visiable property to achive this. Wonderlaura.com is an amazing help. Here is her video on creating tabs that helped me acomplish this. https://www.youtube.com/watch?v=NdiQ802dG3E&feature=youtu.be an the related blog post. https://wonderlaura.com/2018/01/03/powerapps-tabbed-sharepoint-form/
I am looking for the same capability that is available with Content Types using either the Default forms or InfoPath forms: when the New button is clicked, a menu of content types is displayed. When one of them is picked a form with just the fields in the selected content type displayed. With PowerApps Form Customization, all fields in the list are included on the initial form. The list of fields available for the custom form does not include the Content Type so there is no way to hide or disable fields based on the selected Content Type. I see no way to know what Content Type was select form the menu.
I reckon this is a must have function as Microsoft want us to move from InfoPath, and actually just InfoPath is capable of doing it.
Not exactly an answer for PowerApps, but if you are looking for Modern UI forms that can do it - our solution Plumsail Forms creates forms for each Content Type out of the box.
Dear MS - don't make us beg for sensible functionality. This seems an unnecessary and debilitating limitation - one of many - in O365, which is supposedly a tightly-interconnected enterprise environment.
thanks for wasting days of my time once again chasing down convoluted functionality.
Another great example of how we're pushed to using a platform that isn't complete. InfoPath, as horrible as it was, could handle content types. Trying to customize a form (because a required lookup field automatically picks the first item on the list and you can't change that) and you cannot use the built-in features of SharePoint that makes it useful like content types with the new hotness they call Power Apps. Another feature that is "under review" but should have been there on day 1. Another feature where we're coming up with hacks and workarounds because Microsoft continues to deliver a partially finished tool. Might as well just go back to writing .NET code or React apps instead of trying to "leverage" the platform as the platform continues to be a partially implemented mess.