tag:blogger.com,1999:blog-5719332149137711434.post7048768898557908041..comments2024-02-22T23:24:18.865+11:00Comments on Leon's CRM Musings: Setting Multi-Level Categories Against a Record CodelesslyLeon Tribehttp://www.blogger.com/profile/05713816319075495059noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5719332149137711434.post-68067443369911675322012-01-27T21:08:59.218+11:002012-01-27T21:08:59.218+11:00Genius!
You've prompted me to write a blog pos...Genius!<br />You've prompted me to write a blog post about how I did something similar recently using an option set and a lookup, and I'll definitely be referring people here to consider this alternative.<br /><br />Lesser mortals would have created three custom entities for the natural hierarchy of this, but a single entity with a self-referential relationship so you can actually use this for any number of levels iteratively is brilliant!<br /><br />I've used self-references for other things such as creating projects and follow-on projects, or memberships or licences and their renewal periods, or simply to 'clone' service cases. Never considered them for this kind of use though.<br />Definitely one for the toolkit.<br /><br />Keep up the great work.Adam Verohttps://www.blogger.com/profile/07028576607600204087noreply@blogger.com