Has anyone built a control similar to the new form component control? I'd really love to be able to embed a tab from a related form, but need more control over how it happens (i.e. empty state, styling - the current control doesn't show single component tabs). Is an iframe as good as I'm going to get?
I haven't tried yet myself, but yeah, an IFrame is as good as it's going to get because the FCC replicates not only the layout but also form actions, business rules, even formscript. So with any other approach you might try, you'll just wind up having to reproduce an insane amount of functionality that the OOB form experience gives you. Frankly, that's probably all the FCC is anyway.
So I've started down the iframe path - but I'm getting global notifications in the record.... Anyone aware of how to turn these off for a particular form?
Hi @skoofy5 ,
I would like to know about the limits where the Form Component Control doesn't fit.
The FCC is hiding the borders anyway. You could design a form dedicated for this, where the section header is hidden, there is only one control inside and label is hidden too.
What style doesn't fit to your use case?
Chiefly, I wanted to have a little more control over the empty/initial states without having to introduce form logic, because I don't really want system customizers to have to manage multiple steps. Also "source record not selected" isn't super helpful or informative or how that doesn't go full page on this single component tab. It would also be great to open a modal to do a quick create from this control, I mean it does sit on a lookup field...
The second issue is around sizing - the control isn't rendered as 100% height. Which you might be able to see in the image below. I can hack it by doing a calculated height, but I really would love if it the form component boundary was 100% and I could manage my component to just be responsive...
Thanks a lot @skoofy5 🙂
I see what you mean.
Just a few thoughts...
For the "create" issue, you could place the same lookup just above the Form Component Control (FCC) . You could even hide the FCC if the value is not set (if the text is an issue).
Alternative you could autoopen the lookup when the user changes to this tab (only if the lookup is not set).
For the resize issue: if the FCC is used only to show a dataset PCF, i guess you use the FCC only to filter the records on the FCC lookup. If that's the case, maybe it's easier to change the PCF and let it accept 2 more properties: hostEntityName and hostEntityId. Then you can use the PCF directly on the host form (without FCC), and filter the data insids the PCF, using the dataset filtering possibilities.
Hope it helps!
The aim was to try and reduce complexity for future customizers. The FCC got me a lot of the way there, but just doesn't do the last few things I need or allow for that customization I'm after at the moment.
You're right I can use PCF directly on the host form and that's the current approach, was looking for smarter options that reduced customization.
Thanks for the help though guys and was nice to understand the component limitations.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.
At the monthly call, connect with other leaders and find out how community makes your experience even better.