Exam PL-600 topic 2 question 28 discussion

I passed the test today and I'm pretty sure the answer to this question is a B. Thank you very much to the friends in the exam topic and the comment area for providing correct answers. I also want to help everyone, hope my answer is useful to you.

I believe the key lies in 'wants to apply the business rules to all forms in the app.' Therefore, I think a combination of PCF (PowerApps Component Framework) and BR (Business Rules) is the best solution.

Answer B

A. PCF has another purpose, while it could cover some aspects of java scripts. too simplistic B. sounds like the right and weighted answer, but what if the javascript does something you cannot do with the BR (works onload) C. i have seen this scenario once, and it was a good solution because it has all logic in one place. disadvantage: it is certainly not the answer microsoft wants to hear! D. it depends how you understand it: if it includes to remove as much of javascript and put it into the BR to leave only to the javascript what the BR is unable to do, maybe this is a good answer, but you may remain with logic information that is put into separate places. overall it speaks of froms (plural) and form that has BR (singular). I think the problem here is NOT BR and javascripts interfering but rather that some forms have javascripts that could be replaced by BR. Therfore I go for B.

Per ChatGPT

For me D. PCF has nothing to do with the logic. C should be the best practice but we are in low-code Microsoft word.

All of the answers proposed are just flat out wrong. PCFs are not about Business Logic, we should always seek to use out of box functionality over custom code. D is the least incorrect out of all of them. It should be worded better to ensure your Business Rules apply to All Forms and use JavaScript only as a fallback where BR cannot handle it. PS.. I hope this isn't on my exam, if it is I will be commenting on it.

For me it's C. PCF's are custom UI's over a single form control and are limited to the data of that single control. So they have nothing to do with business logic (like showing hiding fields/tabs depending on other fields or the users security roles, making a set of fields required or not depending on some conditions, etc...) Mixing business rules and JS is a quick path to making a system unmaintainable, especially when they start "fighting" over the same fields and events. Also they're entity specific. You can't create a business rule that applies to all forms. So the only answer is JS. It's maintainable (in the right hands) + it can be totally generic or dynamically configurable if needed.

I would argue 'A', the logic from BUSINESS RULES must be applied to all forms in the APP, not the entity, if you use B (business rules) they apply at the entity level only and the logic is already stored there so there would b no need to change it.

Answer is B

answer is B

PCF can be reused and remaining requirements should be handled by Business Rules on individual forms

New business rules by default apply to all forms/whole table. JavaScript resources can be reused on multiple forms easily, as long as the web resource is added to each form's library. For use, controls are powerful, but they can be confusing for users as they are not without faults and bugs (in my limited experience). Implementing business logic with PCF would probably require developing custom components--which definitely does NOT meet the business requirement that the simplified form set up must improve maintainability. The reference page on Microsoft's website explicitly mentions that this is a functionality for developers, not for no-code/low-code super-users. My answer is D. JavaScript can be used, but it should never be used where a business rule works. PCF doesn't seem like it meets the maintainability requirement.

Correct

the key is reusability. Business logical to be applied to all forms, the problem is javascript, so use PCF to replace it.

My choice is D

D is the only one that make sense. PCF is not technology to handle form business logic, it's a framework to build custom UI / UX inside power platform definitely not to write any business rules on the form and the question is pretty clear for me - we are talking about business rules, so e.g. 1) if record type is "VIP" show field X <- can be handled by BR 2) if related Customer if of type "VIP" make X field required <- can't be handled by BR, so JS has to be used to get related customer data. So 60% of people in comments are saying that you should go with PCF to implement 2) rule. Does not make any sense, would like to see a project where somebody does it like that, it would be the worst project on earth...