You’re offline. This is a read only version of the page.
Hello Everyone,
I have a requirement to restrict an Account from having multiple Service Offerings associated with it if those Service Offerings link to the same underlying Service Master record.
The custom C# plugin code is complete, compiles successfully, and is correctly deployed to the Dataverse environment. However, we are currently blocked at the final deployment step: registering the plugin step in the Plugin Registration Tool (PRT).
When attempting to register the step for the Associate message at the PreValidation stage, the official Microsoft PRT consistently rejects the configuration with the error: "Invalid Primary Entity or Secondary Entity specified. Please re-enter the data."
I have tried exchanging the primary and secondary entities but the tool doesn't take both of them as primary entity. The logical names are for sure correct.
Service Offering has a lookup column (Service Name) to Service Master table. Account and Service Offering has got Many-Many relationship
When registered without primary and secondary entity, I am able to achieve the primary task of restricting an account having multiple service offerings of same underlying Service Master record. But the association to fresh and New Account error out.
What exactly have to be checked here? I have ran out of options 😭
Share
Report
All responses (
Answers (
101
