We have 3 tables:
- Table A: List of Projects with a fields about the projects + lookup field from Tasks
- Table B: List of Employees with fields about the employee + lookup field from Tasks
- Table C: List of Tasks with fields about the task + lookup field from Projects+ lookup field from Employees.
We’ve have a calendar interface to show Tasks and want to color code the calendar item by the Project it’s associated to. Since it’s a lookup field and not a single select field, we can’t do this natively, so have to do it by configuring the color conditions.
This is very simply done by:
Where Project has any of ProjectBob set the color to Blue, etc.
It works perfectly in Sandbox. When it’s published to Production, it doesn’t work. We’ve tested it with just a single condition to ensure there weren’t any nested condition problems and it still doesn’t work.
The only thing I can think of is that the “has any of” condition works through a reference value set in Sandbox and since our Production and Sandbox don’t have identical data, they don’t have identical reference values. (note that if we switch the condition to contains ProjectBob, it works). The problem with using contains is that you have to correctly type out the project name. It’s annoying. This seems like a huge oversight since you expect Sandbox data to get “dirty” with insertion of test data. The whole point of a sandbox, hence the name, is dirt.
The same problem with “has any of” happens with any filters we build also.
Is there something we’re missing?
