A feature gap between the current itinerary system and Planner 2.0 itineraries that didn't allow for fields from the departure client's contact record to be used (e.g., p15_clientid.p15_contacthouseholdid) has been addressed.