We need to create a way to capture the global parent account on the account entities for reporting. Since the accounts were already created, this would need to be enforced after the fact. This solution will work if you need to create a data relationship for any fields you want to add. It is not an elegant solution, but it works. The attribute or field that was created needed to have a relationship tied to the account. So, I created a many to 1 (N:1) attribute to hold the global parent f ield. I made this field a business recommended, as it would be on all forms. The workflow, that I will explain later, can be set to fire on an account create action to tie the created account to the global parent account. Here are the settings of the attributes. Since there was already a parental relationship set with the account entity, a referential enforced relationship would have to be created. In t his instance, this will be fine, as we do not want a tied record to be altered if the global pa...
Looking to the world of Microsoft Dynamics CRM, Dynamics NAV, Scribe Insight, SCCM, and other server applications.