Our greatest weakness lies in giving up. The most certain way to succeed is always to try just one more time. Thomas A. Edison
I came across an annoying bug, I couldn’t rename the Default business unit because the parent business unit is mandatory.
History of default business unit renaming
The renaming of business units is a long and extremely interesting subject…..said no one ever.
The default business unit or parent business is automatically created using the name of your organisation. In CRM 4 I don’t think you could rename any business units.
In CRM 2011 they allow you to rename business units which were not the default
CRM 2011 – You can rename and delete business units
In CRM 2013 (according to my study notes) you couldn’t rename the default business unit in CRM 2013
CRM 2013 – MB2 703 – Manage user access, Teams and sharing
Another interesting fact
default business unit team cannot be re-parented, deleted or renamed and it’s members cannot be modified.
In CRM 2015 you could rename the default business unit, well it’s possible but Microsoft make it difficult for you to do because the parent business is a mandatory field but if you are editing the default business unit it has no parent business unit, which means you can’t save the record.
CRM 2011 forms?
I tried using God Mode JavaScript shortcut but this didn’t work and I’m guessing this might be because this form is an old school CRM 2011 style form? What is it doing in CRM 2016!
You can see the annoying required Parent Business unit field
Solution
There are a few ways to resolve the problem but the easiest way is to go to
- Settings –> Customization’s
- Entities –> Business Unit
- Open the field – Parent Business – parentbusinessunitid
- Change the Field Requirement from business required to optional
- Save and publish customisations.
- Change the name of the Default Business Unit – Save
- change the Field Requirements of the Parent Business field back to required and publish
Mission accomplished
If at first you don’t succeed, try, try again. Then quit. There’s no point in being a damn fool about it. W. C. Fields
Filed under: CRM 2011, CRM 2013, CRM 2015, CRM 2016
