{"id":1912,"date":"2022-03-25T15:16:55","date_gmt":"2022-03-25T15:16:55","guid":{"rendered":"https:\/\/www.toponecrm.com\/blog\/?p=1912"},"modified":"2022-03-25T16:40:09","modified_gmt":"2022-03-25T16:40:09","slug":"how-to-make-read-only-show-and-hide-and-other-conditions-to-fields-in-project-operations","status":"publish","type":"post","link":"https:\/\/toponecrm.com\/blog\/dynamics-365\/how-to-make-read-only-show-and-hide-and-other-conditions-to-fields-in-project-operations\/","title":{"rendered":"How to make Read Only, show and hide and other conditions to fields in Project Operations?"},"content":{"rendered":"\n

Go to solutions and open the entity that contains the field you want to make read only and click on Business Rules<\/strong><\/em> and Click New<\/strong>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Business Rule designer window opens with a single condition already created for you. Every rule starts with a condition. The business rule takes one or more actions based on that condition<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Add a description, if you want, in the description box in the upper-left corner of the window.<\/p>\n\n\n\n

Add conditions. To add more conditions to your business rule:<\/strong><\/p>\n\n\n\n

a. Drag the Condition<\/strong> component from the Components<\/strong> tab to a plus sign in the designer.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

b. To set properties for the condition, click the Condition<\/strong> component in the designer window, and then set the properties in the Properties<\/strong> tab on the right side of the screen. As you set properties, an expression is created at the bottom of the Properties<\/strong> tab.<\/p>\n\n\n\n

c. To add an additional clause (an AND or OR) to the condition, click New<\/strong> in the Properties<\/strong> tab to create a new rule, and then set the properties for that rule. In the Rule Logic<\/strong> field, you can specify whether to add the new rule as an AND or an OR.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

d. When you’re done setting properties for the condition, click Apply<\/strong>.<\/p>\n\n\n\n

Add actions. To add an action:<\/strong><\/p>\n\n\n\n

a. Drag one of the action components from the Components<\/strong> tab to a plus sign next to Condition<\/strong> component. Drag the action to a plus sign next to a check mark if you want the business rule to take that action when the condition is met, or to a plus sign next to an x if you want the business rule to take that action if the condition is not met.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

b. To set properties for the action, click the Action<\/strong> component in the designer window, and then set the properties in the Properties<\/strong> tab.<\/p>\n\n\n\n

c. When you’re done setting properties, click Apply<\/strong>.<\/p>\n\n\n\n

To save the business rule, click Save on the action bar.<\/strong><\/p>\n\n\n\n

To activate the business rule, select Activate on top of the screen.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

Go to solutions and open the entity that contains the field you want to make read only and click on Business Rules and Click New. The Business Rule designer window opens with a single condition already created for you. Every rule starts with a condition. The business rule takes one or more actions based on that … <\/p>\n

Continue reading “How to make Read Only, show and hide and other conditions to fields in Project Operations?”<\/span><\/a><\/p>\n","protected":false},"author":18,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_price":"","_stock":"","_tribe_ticket_header":"","_tribe_default_ticket_provider":"","_tribe_ticket_capacity":"0","_ticket_start_date":"","_ticket_end_date":"","_tribe_ticket_show_description":"","_tribe_ticket_show_not_going":false,"_tribe_ticket_use_global_stock":"","_tribe_ticket_global_stock_level":"","_global_stock_mode":"","_global_stock_cap":"","_tribe_rsvp_for_event":"","_tribe_ticket_going_count":"","_tribe_ticket_not_going_count":"","_tribe_tickets_list":[],"_tribe_ticket_has_attendee_info_fields":false},"categories":[9],"tags":[27],"ticketed":false,"_links":{"self":[{"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/posts\/1912"}],"collection":[{"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/comments?post=1912"}],"version-history":[{"count":5,"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/posts\/1912\/revisions"}],"predecessor-version":[{"id":1963,"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/posts\/1912\/revisions\/1963"}],"wp:attachment":[{"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/media?parent=1912"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/categories?post=1912"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/toponecrm.com\/blog\/wp-json\/wp\/v2\/tags?post=1912"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}