![\"image\"](\"https:\/\/license.citruslime.com\/cs\/blogs\/crmcs\/image_7D0402DF.png\" "\\"image\\"")
<\/a><\/figure>\n\n\n\nThis will typically include a pair of Bucket and Record Rules defining a Document Library as the \u2018bucket\u2019 to place each new Folder for an Account Record.<\/p>\n\n\n\n
These rules will currently be non-conditional and so running for all Accounts – so our first time is to make these two conditional.<\/p>\n\n\n\n We can open both our Rules and look at the list of Conditions for each Rule.<\/p>\n\n\n\n For a Non-Conditional Rule, this will be blank.<\/p>\n\n\n\n In Power Apps this is a Many-to-Many relationship between the Rule and the Condition – so we can attach an existing Condition we have already defined, or create a new Condition for our logic.<\/p>\n\n\n\n We can start from scratch by creating a new Condition to only carry out this Rule if the [Relation Type] field is not \u2018Customer\u2019.<\/p>\n\n\n\n With this condition created, we can attach to both the Bucket and Record Rules:<\/p>\n\n\n\n This then means that only Non Customer Accounts will be valid for these Rules to store documents via the basic Document Library and Folder combo.<\/p>\n\n\n\n Now we can look at defining our alternate flow if the Account is a Customer. We do this by defining a 2nd Record Rule that defines that DocDrive should create a new Team for each Account as per the following:<\/p>\n\n\n\n We then make this Conditional to define which Accounts should be represented by a Team in Microsoft Teams – in my case, a Condition that allow does this is [Relationship Type] is \u2018Customer\u2019:<\/p>\n\n\n\n With this combination of Conditional Record and Bucket Rules our Entity Definition will look like:<\/p>\n\n\n\n We can then create new Account Records to test how this works for our Customers and Non-Customers.<\/p>\n\n\n\n Starting with Non-Customers, we can track a new Account and review the Location created for us in SharePoint.<\/p>\n\n\n\n Whereas if we create a new Account and flag the Relationship Type as Customer, this will create differently into SharePoint or in this instance, MS Teams.<\/p>\n\n\n\n We can see the result in Microsoft Teams:<\/p>\n\n\n\n Or by clicking Location to browse into SharePoint directly:<\/p>\n\n\n\n On key element is that often an Account or other Record will upgrade or qualify to a Key Account in Dynamics, and so go from meeting the original set of Conditions to a different Condition.<\/p>\n\n\n\n If or when this happens, the logic in DocDrive will pick up on the change and adjust the Document Location automatically.<\/p>\n\n\n\n So if test it an initially non-key account:<\/p>\n\n\n\n This is reflected as a Folder in SharePoint.<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\nConditional Rules<\/h4>\n\n\n\n
<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\nMicrosoft Team per Account<\/h4>\n\n\n\n
<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\nTesting for a Non-Customer<\/h4>\n\n\n\n
<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\nTesting for a Customer<\/h4>\n\n\n\n
<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\nNon Customer to Customer?<\/h4>\n\n\n\n
<\/a><\/figure>\n\n\n\n