You are developing a model-driven app for a company.
The app must map child records to a parent record.
You need to use the column mapping feature to configure the app.
Which two actions can you perform? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
To map child records to a parent record using column mapping in a model-driven app, you can map the value of a Choices column on the child table to the value of a Choices column on the parent table. This allows both tables to have synchronized choices, ensuring data consistency. Additionally, you can map the value of columns on both the child table quick-create and main forms to the value for the same columns on the parent table, facilitating data entry and reducing user effort by prepopulating fields with consistent data across related records. Remember that the data types and contexts must align for successful mapping.
Are you all serious? B is the MOST WRONG option. Column mapping can set a value of parent table field to the filed of sub table, B does it in reverse. And the wording of 'map xxx to xxx' is very confused than 'set xxx to xxx' I refer to AC.
AC is correct
This question was on my 4/7/23 exam
When you map table columns for a 1:N table relationship certain items of data from the primary table row will be copied into the new related table form to set default values that people can edit before saving. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/map-entity-fields
A and D are not possible. You cannot map a choice value to another choice value as suggested in A. Could there be something wrong with the wording for question B? If it was a choice column the question would make sence.
A is possible "If you need to map choice columns, we recommend you configure both columns to use the same global choice . Otherwise, it can be difficult to keep two separate sets of options synchronized manually. If the integer values for each option aren’t mapped correctly you can introduce problems in your data. More information: Create and edit global choices for Microsoft Dataverse (picklists)"
I think AB. You dont map relationships based on Forms (C).
I think the answer is AB
AC is correct
AC are correct
A and C are the correct option because, If you map to or from a column that isn’t displayed on a form, the mapping won't be done until the column is added to a form. Option C says the the fields on the "Quick Create" & "Main" form.
For me, B is correct but with C I have doubts because it is possible but it is not a certain.
I think it's BC. I guess C means "map the column present in those forms to the other entity". Map relationship is not based on forms but on columns, ok, but I guess they talk about "columns present in those forms"... who knows? Only Microsoft