Exam PL-200 topic 1 question 51 discussion

Another stupid question. Why would you delete a related contact when deleting a custom table record, and why you wouldn't ?. Actually the answer will depend on above context. Which doesn't say in the question (must be in mind of the person who wrote it)

Should be Restrict for Delete and Cascade for Share

Since the question is about what happens in the child table (not the parent table), the only options are: - Delete: Cascade All - Share: Cascade All https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships#parental-table-relationships See the column for "Parental".

Custom table record is deleted → Cascade All This ensures that when a parent record (contact) is deleted, all related child records in the custom table are also deleted automatically. Custom table record is shared → Cascade None This means that when a parent record is shared, it does not affect the child records. The child records maintain their existing permissions and are not automatically shared.

This question is missing context i.e what do you want the use case to be? then we can point it to the correct behaviour as far as i'm aware there is 6 table behaviours that exist. 1. Cascade active: Perform action on all related table records. 2. Cascade all: Perform action on related table records 3. Cascade non: Do nothing 4. Remove link: Remove the lookup value from all related records 5. Restrict: Prevent the primary table from being deleted when a related table record exist. 6. Cascade user owner: Perform action on all related table records owned by the same user as the primary table.

1. Restrict 2. Cascade None https://learn.microsoft.com/en-us/power-apps/developer/data-platform/configure-entity-relationship-cascading-behavior

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships If custom table is Not Parental, then it's Restrict and Cascade None. For example, if you create a new custom table and add a 1:N table relationship with the account table where your custom table is the related table, you can configure the actions for that table relationship to use the options in the Parental column. If you later add another 1:N table relationship with your custom table as the referencing table you can only configure the actions to use the options in the Not Parental column. One problem I have is this: A custom table can't be the primary table in a relationship with a related system table that cascades. This means you can't have a relationship with any action set to Cascade All, Cascade Active, or Cascade User-Owned between a primary custom table and a related system table. Not sure if the table is a system table that cascades?

1 - Restrict 2 - Cascade All

It depends on the behavior you want and this is not stated in the question, so it could be anything

most probably: the contact table is the parent table and the custom table is adding informatiion to and about the contact. delete contact --> restrict share contact: depends if the others should see sub-records or not. maybe yes. then cascade all is most probable. so everyone can see the details of the contact too.

Assuming that the custom is the child from the contact (parent), because you configure a child table relationship from there with to the (parent) account (while you are in the custom entity). Most probable scenario. As remove link is not an option: 1) deleted - restrict. 2)sharing: parental is Cascade all. (https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships#parental-table-relationships cascade non is not-parental). And it is more a priviledge discussion... A custom table can't be the primary table in a relationship with a related system table that cascades. This means you can't have a relationship with any action set to Cascade All, Cascade Active, or Cascade User-Owned between a primary custom table and a related system table. --> would mean you cannot make a structure like house (account), household(custom), and contact? sort of strange. 3/3

The question also is which entity is parent and which one is child, reading “You create a custom table and configure a child table relationship with the contact table.” Sounds a bit like the custom is parent and the contact is child relationship. But this sounds odd (maybe you have some scenario where account is the house, custom entity is household (many households in 1 account(house), and many contacts in 1 household.). Or is the custom table the child record and the contact is the parent? not sure. One-to-many custom -> Contact works with referential and delete restrict or remove link as an option only (creation works). 2/3

I think this answer is wrong. Because when I want to create a One-to-Many relationship from Custom to Contact (contact lookup field). for share and unshare option 'restrict' is not available just:  Cascade All  Cascade Active  Cascade User-Owned  Cascade None For parental and Custom (Delete cascade all) i get an error: Contact is parented to entity with id... (probably account) and name contact. Cannot create another parallel relation with Entity: custom entity. No new relationship can have any action set to Cascade All, Cascade Active, or Cascade User-Owned if the related table in that relationship already exists as a related table in another relationship that has any action set to Cascade All, Cascade Active, or Cascade User-Owned. This prevents relationships that create a multi-parent relationship. (1/2)

1- Customer table record is deleted: A- Restrict This will prevent the customer table record from being deleted if there are any related records in the contact table. This will preserve the data integrity and avoid orphaned records. 2- Custom table record is shared: B- Cascade All This will share the custom table record with the same users or teams as the contact table record. This will ensure consistent access and visibility across the related records.

Both are Cascade All. Resource: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships

there's no way to answer without knowing what is wants! Not possible.

on exam 20/9/2023