HOTSPOT -
You need to resolve the issue reported by substitute employees after they are assigned service requests.
How should you configure the system? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Box 1: Service Request 1:N Qualification
When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests.
Box 2: Cascade All -
Cascade All - Perform the action on all referencing table records associated with the referenced table record.
Reference:
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/configure-entity-relationship-cascading-behavior
This question was on Sept 24th Scored 712 Selected the same answer
This question was on July 7th Score 806 1- service request 1:N qualification 2- cascade all
on may 2023 exam
Relationship 1- service request 1:N qualification Cascading rule 2- cascade all
correct
Correct
On exam March 2023
N:N, one service request (like background check for xxx) may have multiple qualifications (like education, work location, address, credit) one qualification (like xxx's address) may associate with multiple service requests (banks, hiring companies) 2nd Q: cascade none. If you want delete one service request, should just leave linked qualifications alone
Can you please explain why N:N because the essays says a service request can have 1 or more qualification records associated with it.
Casacade None?..... Try reading this again... it's cascade all.. must be "When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests." Assign Records via Cascade All
Valid line of thinking BUT It never mentions that Qualification records are RE-USED for multiple Service Requests. So the assumption is that they are not. It says Clients enter their data in a website, which then uses a service account to create the records in the Dataverse database. Never says there is some sort of complex previous Service Request / Qualification re-use mechanism in place. Furthermore it explicitly states: In the rare event that results are questioned (by the client), a new service request is created and verified independently of the previous work that took place. INDEPENDENTLY OF PREVIOUS WORK - so again assumption is that a brand new Service Request and Qualification records are always created. Also if you don't use Cascade All then there is no way (mentioned in the answer) to fix the issue of users not being able to see Qualification records.
I initially thought 'Cascade None' for the same reason. Then I realised that cascading behaviour in Dataverse doesn't just apply to deleting records, but also to assigning, sharing, merging, etc. In which case, 'Cascade All' is correct. See https://learn.microsoft.com/en-us/power-apps/developer/data-platform/configure-entity-relationship-cascading-behavior#using-sdk-for-net-to-configure-cascading-behavior