Exam PL-400 topic 6 question 18 discussion

Associate, none, none, sycn is the correct answer

When you register a plugin on Associate message, you have to leave “Primary and Secondary” entities as ‘none’.

I just tried this and what is mentioned by btmeera is correct: Associate None None Sync (If you select associate in PRT and try to assign a primary entity you will get an error)

Message: update Primary Entity: contact Secondary Entity: none Execution Mode: synchronous

Update Contact None Synch

Message: update ("Customer preferences" must be stored in the Contact entity) Primary: Contact Secondary: Region and None are sense, but Region is more sense for validation Sync

Multi Select OptionSet .... Ringing a bell ? lol

Associate, none, none, sycn

"You need to register the plug-in to meet the requirements." ... so I understand its about registraiton https://learn.microsoft.com/en-us/power-apps/developer/data-platform/tutorial-write-plug-in#register-a-new-step So it's correct: Create, Contact, Region, Synchronous Almost all post here is about method to perform data operation - Create, Retrieve, RetrieveMultiple, Update, Delete, Associate, and Disassociate

There is difference between 1- How the question is requesting the design? 2- What's the best practice? In order to answer Q1, the answer is Update, Contact, None, Synchronous, where the contact entity has 3 lookup fields to the region entity called [Travel Preference 1 - Travel Preference 2 - Travel Preference 3], since the question is mentioning "Customer preferences must be stored in the Contact entity" To answer Q2, the answer is to register the plugin-in on the Associate message in the pre-validate pipeline, with primary and secondary entities = None, and execution mode same as Q1, Synchronous. For me, I will answer the question as it is and go with Q1: Update, Contact, None, Synchronous

Update Contact none Sync Customers are allowed to add up to three regions << this is unclear, but to me this sounds like the number of available regions are already predetermined (three), which mean it's possible that "preferences" is an optionset. Customer preferences must be stored in the Contact entity. << already a clear indication that Contact entity is the one getting updated. Lastly it has to be sync because we want the error to appear if the validation failed. Async will not throw an error on screen.

Associate will not store the preferences info in Contact Entity... It seems that preferences are simple lookups fields on contact entity, so correct message must be "Update". In my opinion: "Update" (preferences stored in contact entity), "Contact", "None", "Syncronous" (must be throw an error to user if data wrong)

So, it seems we agree on "sync"... About "Associate, none, none": This plugin will fire on *any/every* entity that gets associated with *any/every* entity. Do we really want a plugin firing *ALL* the time???

The wording of the question makes this tricky: "Customer preferences must be stored in the Contact entity" - this makes me think that the region data is not an secondary entity (for example Multi-select option), hence the contact has to be updated not associated with another entity. if that is the case the message would be update, primary entity - contact secondary - none Execution would be synchronous because we would need to validate the data and display error message in real time - "An error message must display if customers enter data incorrectly" I can also see it the other way where the region is a separate entity and then you would have to associate these with a contact. If this is on the exam I will go with my gut feeling and go with update

According to this link - https://docs.microsoft.com/en-us/power-apps/developer/data-platform/register-plug-in , Secondary Inage "This field remains for backward compatibility for deprecated messages that accepted an array of EntityReference as the Target parameter. This field is typically not used anymore." so null sounds right

isn't Associate/Disassociate messages only for N-N relationship adding only? https://community.dynamics.com/crm/b/mylifemicrosoftdynamiccrm/posts/ms-dynamics-crm-associate-disassociate-message-plugin

What about "update, contact, none, synchronous"? Just curious...