In my model-driven app, I have a form for a table that has a Form Component Control on a tab. That FCC is for the parent (1:n) table. It works well, except that quite frequently I get a "source record not selected" message displayed instead of the parent table form. If I refresh the page, the parent form displays and works fine.
It seems like a timing issue. The FCC is trying to render before the lookup field it is applied to has a value populated. Something like that.
Any ideas how I can get this to work more consistently?
Solved! Go to Solution.
I just got off the phone with Microsoft support. They confirmed that it's a known issue and a fix is coming to my region (North America) in the 3rd week of June.
Interesting @tschopp ,
I didn't saw that behavior until now, so it might be a special case (or a new issue).
Maybe the parent lookup is the first control on the page (so the focus is somehow still on the control)? I've seen weird issus for long time because of this (of course, not related to the FCC).
What if you set the value for the parent lookup using the console. Does it load then?
Just type something like Xrm.getAttribute(....).setValue(.,..)
Or maybe change the value for the parent using the control, and then change it back. Does it work?
Do you have the parent lookup on the form, without having it rendered as a FCC?
I do not. Do you think it would make a difference if it was there?
I added the parent lookup on the tab so that it's now there twice, once as FCC, once as default control. That seems to make the error happen more frequently!
Hi @tschopp ,
I've tried to place a FCC for the ParentAccount on my Opprtunity form, but I cannot reproduce the issue.
I've even tried to throttle my network connection, to see is there is something wrong.
1. Do you use the quick create form for opportunity, or the main one?
2. I understand that there might be something with asyncronous processes. Maybe it's not about showing the FCC too fast (usually it's the last I get displayed), maybe it's a script which deletes the parent in your oppotunity form. Maybe if you attach a script to OnChange for your parent lookup on the Opportunity form, and there make a console.log, you get to know if something happens.
Maybe if you delete that (or try with a new, lightweight form without scripts) you get closer to the issue.
I'm going out of ideas. Of course it could be a bug too..
Hope this helps.
Hi @DianaBirkelbach ,
Still having the issue. Not sure if it matters, but I'm using 2 custom tables that have a 1:N relationship.
1. I'm using Main forms for both tables.
2. I tried adding script to the parent lookup OnChange event and it never fires. I put a debug breakpoint in to be sure.
Not sure what else to try before going to Microsoft to report it as a bug.
Hi @tschopp ,
I have no idea what else you could try. It's still a preview, so for now is no guarantee, but maybe a bug report would help.
@HemantG : Is this a known issue or something somebody from the team would want to have a look to?
So many events that are happening this month - don't miss out!
Explore the latest innovations, learn from product experts and partners, level up your skillset, and create connections from around the world.
Your chance to join an engaging competition of Power Platform enthusiasts.