I have no desire to start tinkering with Relationships List to add my own meta data, or creating a Relationships list of my own.
Things can be much simpler than that as detailed below.
Conditional formatting has always been a pain point in Share Point 2013 and Share Point Online (Office 365).
use some calculated columns Java Script to apply conditional formatting to the row).
There are lots of blog posts about that, but the main problems with all of those are amount of time you have to invest to produce the result and the fact that it is practically out of bounds of the regular Share Point user.
section to the field and hardcode the various Id’s that define a term set (required if you are using a sandboxed solution), or configure these in code.
I’m taking the code approach here as it is the only way to ensure the field will work across multiple environments.
To recap on the previous post we are aiming to avoid the following problems when creating Share Point 2010 taxonomy fields through features: We found the first problem was due to a missing note field when creating a list definition that used the site column.