Share
Report
40Hello, Microsoft Community,
I am working on a business rule to lock fields that are not part of the active stage in our business process flow, ensuring that only fields relevant to the current stage are editable.
I have attempted to achieve this by creating a business rule with the following configuration:
- Scope: All Forms
- Condition: Check if the Business Process equals /Sales Process/ and the stage is, for example, /Qualify/. (We do not use the lead entity, this is why we are using the sales process instead of the lead to opportunity)
- Action Lock a specific field (Field Name) (not part of the active stage).
The business rule functions as expected when it is set to lock a single field.
However, the problem arises when I attempt to add another field to be locked under the same conditions. Once a second field is added to the rule, it stops working altogether—none of the specified fields get locked.
Steps Taken:
- Verified the conditions to ensure they correctly identify the active stage.
- Checked for any logical errors in the rule configuration.
- Attempted with different fields to rule out the possibility of field-specific issues.
Despite these efforts, the issue persists, and I am currently at an impasse. It's crucial for our workflow to have this functionality working seamlessly across multiple fields within each stage of our sales process.
Questions:
1. Has anyone encountered a similar issue, and how was it resolved?
2. Are there any known limitations or bugs with business rules in Dynamics 365 CRM that might be affecting this functionality?
3. Could there be a more effective method or alternative approach to achieve the desired outcome (locking fields based on the active business process stage)?
I am open to any suggestions, workarounds, or insights into how this might be resolved. Detailed explanations or links to resources are highly appreciated.
Thank you in advance for your time and assistance!
All responses (
Answers (
