MDA Embedded Map showing "Source record not selected" error message

[CosmoKramer]

Hello all,

I have a Model Driven App with a Main Form of type 'SYSTEM Contacts' which contains a MAP Form Component. When I run it by itself it works perfectly, as shown below in the 1st image, but when I embed that Form into a Custom Form, a "Source record not selected" error message appears as shown in the 2nd below image.

Working...

Not working...

The following URL provides hints of what it could be causing it, but not exactly my scenario.

• Edit table records directly from another table’s main form - Power Apps | Microsoft Learn
• Relational data on Model-driven forms, part 2: Form Component Control - Jukka Niiranen

Any ideas on what is causing this error?

Cheers,

Cosmo Kramer

[CosmoKramer]

Continuing with my troubleshooting of this problem, I have with no change to my Form display:

a) Enabled this 'Admin Center' setting

b) Turned the MAP Table into a Canvas App and then embedded that into the other Table's Main Form

c) Discovered this sentence in "Embedded canvas apps are not displayed when creating a new row since they need a row context to be passed to them." Guidelines and troubleshooting when working with embedded canvas apps - Power Apps | Microsoft Learn 

Question: So how do I pass a dummy new row to this embedded SYSTEM Form that contains a Bing MAP Form Component to make it display??

Any suggestions??

Cheers,

Comso

[CosmoKramer]

Performing some more investigation into this error, https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/form-component-control#record-s... states...

“The form component control doesn't support embedded form component controls, such as adding a form component control to a form that is used by a form component control” -> Bingo!!!

So if anyone else can understand this sentence, does this mean NO SYSTEM Forms with fancy Form Components (e.g. MAPS & AI) can't be embedded in this way???

Cheers,

Cosmo

[LinnZawWin]

@CosmoKramer 

Let's consider the "Form Component" control as a Quick View Form but with editable capability.

If you have an "Animal" lookup and want to show the fields from the Animal table as a Form Component, you need to add two "Animal" lookups to the form. One to allow the user to select the value for "Animal" lookup and another one to be shown as the "Form Component"

In the first screenshot, I have a Contact lookup but no value, so the form component is showing the message "Source record not selected"

Once I select the value for the lookup, the Form Component shows the fields for the selected Contact in the lookup.

To summarise, you are getting a "Source record not selected" error message because you have not selected any record for that lookup.

[CosmoKramer]

Ahhhh...

1) I'm trying to use this embedded 'Contact' SYSTEM Form which has an embedded Maps Form Component initially as a user entry Form to enter the new address of the discovered injured native animal. In my next Form, this embedded Form will be used to display theses entered addresses.

Question: Can I use this embedded Form in this manner?

2) In this Contact SYSTEM Form which I have cloned to make the 'Animal Location' Table (below), I have changed it's original Primary Key from 'Full Name' to 'Location Id' as a Auto-Incrementable number.

Question: When I run this Form by itself, the Primary Key increments perfectly, but is it okay to use it in a Relationship how I have it?

3) I actually already have two Lookup Columns created from the Main Form pointing back to the same above mentioned Primary Key in the 'Animal Location' Table.

Question: Does all the below Table/Lookups look okay to you?

Cheers,

Cosmo

[LinnZawWin]

1) That is probably a bad idea to use the Form Component control for such a requirement. It is better to re-create the address columns in your Animal Location table and add a map control.

2) The relationship will just link to the GUID column of the table, so it does not matter how you update the Primary Column of your table.

3) Yes, it looks good. When I do table configurations, I normally create a lookup column instead of creating relationships. (unless I have to create N:N relationship)

[CosmoKramer]

1) Ack

2) Ack

3) Those Relationships objects were automatically created when I created the Lookups -> I didn't manually create them.

Thank U 🙂

[CosmoKramer]

In regards to your above #1 response "That is probably a bad idea to use the Form Component control for such a requirement. It is better to re-create the address columns in your Animal Location table and add a map control." -> This is how the below cloned 'Contacts' Table has been configured. But I want it embedded within my Application's main Form (as shown below). But when I embed that System Table, it only displays that error message.

Is this what you were meaning??

Cheers,

Cosmo

[LinnZawWin]

@CosmoKramer 

My recommendation was to "re-create the address columns in your Animal Location table and add a map control". That is not related to embedding the form into another form. (because to embed the form component, you need to have the lookup to the parent record and you need to select the lookup value to get rid of that error message.)

It is just creating new columns in the Animal Location and adding those to the Animal Location Main Form together with the map control.