{"id":20001,"date":"2019-07-29T12:20:24","date_gmt":"2019-07-29T12:20:24","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=20001"},"modified":"2022-07-21T12:15:48","modified_gmt":"2022-07-21T06:45:48","slug":"how-to-use-scope-with-common-data-service-in-microsoft-flow","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2019\/07\/how-to-use-scope-with-common-data-service-in-microsoft-flow\/","title":{"rendered":"How to use Scope with Common Data Service in Microsoft Flow"},"content":{"rendered":"

Introduction<\/strong><\/h2>\n

As we know in Dynamics 365 CE, the record access level plays a very crucial role, because it helps users to limit the access to the records in the Organization. This access of records can be to whole Organization, Parent: Child Business Units, Business Unit and User level. In the same way we can specify the scope of Microsoft Flow by using Common Data Service.<\/p>\n

Suppose, if we wanted to trigger a Flow for the records of same business unit users only in Dynamics 365 CE, then we can simply use scope property of Flow trigger step as shown below:<\/p>\n

\"Use<\/p>\n

Given below are the scope descriptions of Flow:<\/p>\n

Organization:<\/strong><\/p>\n

When we select the scope as Organization, then the flow will trigger for all users of CRM.<\/p>\n

Parent: Child Business Units<\/strong>:<\/p>\n

When we select the scope as Parent: Child Business Units, then the flow will trigger only for the Users who are under the subordinate business units of the Flow execution context User\u2019s Business Unit.<\/p>\n

For example, we have User A, User B, and User C. User A is Under Business Unit 1 and User B is under Business Unit 2 and User C is under Business Unit 3. And Business Unit 3 is present under Business Unit 2 and Business Unit 2 is present under 1.<\/p>\n

Given below is the screen of hierarchy:<\/p>\n

\"Use<\/p>\n

So suppose if we have created a Flow and the Flow execution context User is User B then the flow will only trigger for User B and User C, not for User A. It is because User A\u2019s business unit is not under the business unit of the User B.<\/p>\n

Business Unit:<\/strong><\/p>\n

When we select scope as Business Unit, the Flow would trigger for all users of the same business unit. Same business unit means, the Flow execution context Users\u2019 Business Unit.<\/p>\n

User:<\/strong><\/p>\n

When we select scope as User, it would trigger Flow only for a single user who is Flow execution context User.<\/p>\n

Given below is an example of Flow execution user:<\/p>\n

\"Use<\/p>\n

Conclusion<\/strong><\/h2>\n

As shown above, by using Scope with Common Data Service in Microsoft Flow users can limit the access to records in the Organization.<\/p>\n

70% of global 2000 companies apply gamification to improve productivity and returns!<\/div><\/div><\/h2>\n

Gamifics365<\/a> <\/strong>\u2013 Spin the magic of games within Microsoft Dynamics 365 CRM to improve user adoption, enhance productivity, and achieve company goals!<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction As we know in Dynamics 365 CE, the record access level plays a very crucial role, because it helps users to limit the access to the records in the Organization. This access of records can be to whole Organization, Parent: Child Business Units, Business Unit and User level. In the same way we can\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":20008,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[9,16,18,19,28,36,1985],"tags":[1150],"class_list":["post-20001","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-common-data-service","category-dynamics-365","category-dynamics-365-v9-2","category-dynamics-crm","category-flow","category-microsoft-flow","category-power-automate","tag-microsoft-flow"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/20001","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=20001"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/20001\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/20008"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=20001"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=20001"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=20001"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}